Changelog v2.0

[Sander]

The idea is quite simple:
At this moment we don't have anything what is perfectly integrated to the website.

We used to have the Development Blog at the forum, which wasn't really a changelog, and we moved that to the website to make the website more active.
The WIKI, it felt never as integrated. And I really doubt that many users are checking it.

So, make a proposal for a new changelog. Our goal is to integrate it at the main website.

[Matthias]

Why not make another tab in the website in contact > About LVP?

[Sander]

It's not where, the question is how.
And that's up to you.

[Matthias]

Hmm, a normal link wouldn't do I guess?

[Peter]

And how do you suppose to update "a normal link"?

[Matthias]

Sorry for the late reply, seems like I missed the topic. Hmm, didn't think of that . I'll see if I can think of anything else.

[[Griffin]]

Maybe have an edit link somewhere on that page which is only visible to developers, depending on the forum privileges?

[Fireburn]

It would be cool to have it connected with the trac, like the current messages that output in .dev. Gets updated on the spot, and you can use the commit messages as description.

[Sander]

@ Griffin: You mean a forum board / topic which is embedded to the website? Technical possible (The SA-MP.nl newsmessages are actually forum posts). 

@ Fireburn: Trac is indeed cool, and realtime.
The commitlog however is often quite short/cryptic. (Dev specific)
So in this case the next question will be: Do we want technical changelogs, or understandable changelogs for normal players? Or maybe even combined?

At this point I'd say: trac. Any other solution has to be done manually, while trac is realtime, thus it doesn't require extra time.  (Updating the changelog manually.) You have to enter a commitlog anyway

When I started this topic I had trac in mind already, but wanted to hear your opinions.
So far the two best options are here: forum and trac.
Other options: textfile, wiki

And just had another cool idea, although I don't know if trac has a function for it:
Source stats! Number of lines (Comment/Real code?), characters, number of files.