Re: [warzone2100-dev] [Warzone-dev] Changelog changes?
Am Montag, 24. August 2009 02:55:14 schrieb Stephen Swaney: On Mon, Aug 24, 2009 at 12:40:56AM +0200, Christian Ohm wrote: On Sunday, 23 August 2009 at 23:40, Per Inge Mathisen wrote: I like current format. It gives superb traceability of everything in the changelog, and looks really correct. If it is a PITA to maintain for people, I am willing to do it. If you want to use the ChangeLog in official postings, just sed remove everything inside parentheses first to make it look better. I agree with Dennis that the Changelog should give a good overview of the user-relevant changes, and the current copy the svn log the day before a release approach doesn't do a good job of that. The Changelog should be detailed information for developers - exactly what is different in the code from before. Users only care about visible changes. For them, something like GNU's NEWS or Release Notes describes items of interest. The Changelog and Release Notes serve two separate functions and have different audiences. The current Changelog seems fine to me. We never had a changelog-for-developers. Our ChangeLog always was meant to be a changelog-for-users. It was meant to contain user visible changes, with the definition of user partly containing mod authors, too. I never saw sense in having two changelogs, one for the users and one for developers. The latter can look into the svn/git log, and if they cannot, then a svn2cl generated log does not really help them either, without the diffs. --Devu signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone-dev] Changelog changes?
Am Montag, 24. August 2009 00:40:56 schrieb Christian Ohm: I agree with Dennis that the Changelog should give a good overview of the user-relevant changes, and the current copy the svn log the day before a release approach doesn't do a good job of that. Perhaps we could make it a policy to include a changelog entry for commits (for user info, as opposed to develper info in the svn log), and then Per or others who want revisions included can add them later. It sounds like a good idea. However, we already tried this, but since it was never enforced, it did not last long. --Devu signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone-dev] Changelog changes?
Am Sonntag, 23. August 2009 21:23:25 schrieb bugs buggy: It is apparent that the current way we do Changelogs isn't the best way, since it is way more time consuming than it should be. It should present the user a good overview about new features, which existing things important to him have been changed or bugfixed. That is a kind of service and thus implies to take some time. Whether it is more or less than it should be depends on how userfriendly someone is, and how many detail users and distributors want. We could just drop the revision number, and stick with tickets, Sounds reasonable. Especially since the revisions are mentioned in the tickets and also of no importance to the average user. Further they are different for trunk and branches and thus backports will create a mess. or we could use svn2cl to produce the changelog for us. In that case we need to move the current ChangeLog to NEWS (GNU style). Replacing current ChangeLog with an svn2cl generated ChangeLog is definitely not an option to me. The changelog shall be user readable, and also only contain things interesting to the user. It shall be grouped by topics and arranged by importance and significance. That is not possible for a machine to do. Regards, Devu signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone-dev] Changelog changes?
I like current format. It gives superb traceability of everything in the changelog, and looks really correct. If it is a PITA to maintain for people, I am willing to do it. If you want to use the ChangeLog in official postings, just sed remove everything inside parentheses first to make it look better. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone-dev] Changelog changes?
On Sunday, 23 August 2009 at 23:40, Per Inge Mathisen wrote: I like current format. It gives superb traceability of everything in the changelog, and looks really correct. If it is a PITA to maintain for people, I am willing to do it. If you want to use the ChangeLog in official postings, just sed remove everything inside parentheses first to make it look better. I don't mind having the revisions there, but _putting_ them there is a pain when you don't commit to svn directly. I agree with Dennis that the Changelog should give a good overview of the user-relevant changes, and the current copy the svn log the day before a release approach doesn't do a good job of that. Perhaps we could make it a policy to include a changelog entry for commits (for user info, as opposed to develper info in the svn log), and then Per or others who want revisions included can add them later. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone-dev] Changelog changes?
On Mon, Aug 24, 2009 at 12:40:56AM +0200, Christian Ohm wrote: On Sunday, 23 August 2009 at 23:40, Per Inge Mathisen wrote: I like current format. It gives superb traceability of everything in the changelog, and looks really correct. If it is a PITA to maintain for people, I am willing to do it. If you want to use the ChangeLog in official postings, just sed remove everything inside parentheses first to make it look better. I agree with Dennis that the Changelog should give a good overview of the user-relevant changes, and the current copy the svn log the day before a release approach doesn't do a good job of that. The Changelog should be detailed information for developers - exactly what is different in the code from before. Users only care about visible changes. For them, something like GNU's NEWS or Release Notes describes items of interest. The Changelog and Release Notes serve two separate functions and have different audiences. The current Changelog seems fine to me. -- Stephen Swaney sswa...@centurytel.net ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone-dev] Changelog changes?
On Sun, Aug 23, 2009 at 5:40 PM, Christian Ohmchr@gmx.net wrote: I don't mind having the revisions there, but _putting_ them there is a pain when you don't commit to svn directly. That's not a big deal. You don't need to edit the changelog when you commit, you can just read the commit log and add the stuff to the changelog all at once. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
