I'm not entirely clear on what needs to go onto the changelog.
I'm assuing an item changed a number of times would only get one entry?
And changes invisible to the user might not get posted (Say,
PNGcrushing images)?
Can someone write (or point me to) a concise explanation of what
needs to go on the changelog?
I may be guilty of leaving off some items. (i'll check soon)
Also i either missunderstood or recieved conflicting advice about
weather the changelog should idealy be updated in the same commit, or
as an additional one. Which way?
-eleazar
On Dec 12, 2005, at 9:04 AM, David Philippi wrote:
Hi,
I've just had a look at the changelog and noticed that at least the
death animations for the drakes are not listed. I'm rather sure
that other people will forget to update the changelog as soon as
they commit new stuff as well. Looks like we need to make this
requirement more obvious?
Waiting for someone to clean up after you is a dangerous practice
in an open source project. If you lack the time/skill/whatever, ask
someone and get a confirmation that someone else will do it in this
specific case - everytime.
Bye David
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
