Re: [Htmlparser-developer] changes.txt
Brought to you by:
derrickoswald
From: Somik R. <so...@ya...> - 2003-05-10 15:56:45
|
Derrick, This is good stuff! The changes.html had to be done as some of the logs had html tags in them, and they don't show up on the change log page unless they are formatted to use < and > This could probably be done with the ant script.. or you might review if you need to do it at all. Cheers, Somik ----- Original Message ----- From: "Derrick Oswald" <Der...@ro...> To: <htm...@li...> Sent: Friday, May 09, 2003 12:18 AM Subject: [Htmlparser-developer] changes.txt > > OK, I'm going to try using the cvs2cl script to automatically create the > change log for a release. > > That means you don't have to update changes.txt when you drop code. > yeaahhh! > > But, you do have to make the commit messages as good or better than the > changes.txt message was. boooo! > > For guidelines on what to put in commit messages see: > http://www.red-bean.com/cvs2cl/changelogs.html > Remember, the commit messages will now be visible to end users, so try > to use whole sentences and valid grammar. > > Also, the script uses a time window and identical message text to unify > separate file log messages into a chronological sequence of activity. > So, the rule is, drop everything as close together in time as you can > (one drop is best of course, but sometimes it doesn't work that way), > and use the same log message for all files related to a particular change. > > Derrick > > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Htmlparser-developer mailing list > Htm...@li... > https://lists.sourceforge.net/lists/listinfo/htmlparser-developer |