Am Montag, den 12.12.2005, 09:33 -0500 schrieb john w. bjerk: > 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?
Sure, I'd say that everything visible to the user should go into the changelog. > And changes invisible to the user might not get posted (Say, > PNGcrushing images)? I don't think this is important since we're doing it all the time. If a project does it for the first time on a huge base of images, that's another matter. > Can someone write (or point me to) a concise explanation of what > needs to go on the changelog? Would be a good idea to create one. > 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? AFAIK it's better to have the commit to the changelog be a seperate one to make it easier to port changes over to the 1.0 branch. Might also make it easier to revert something. Bye David
