On Sat, 31 Jan 2009 22:30:53 +0100 (CET) Vincent Torri <vto...@univ-evry.fr> said:
yes. NEWS would be a summary of the changelog for a quick 2 minute scan of "whats the important stuff". changelog is for all the nitty details when you get an updated release tarball. > On Sat, 31 Jan 2009, Viktor Kojouharov wrote: > > > from what I've seen in almost every other project, the ChangeLog is > > being used a SVC log mirror. It's the NEWS file that actually reflects > > meaningful changes between versions, not the ChangeLog. > > My point of view (maybe i should have been clearer): > > * in ChangeLog, i would put the important changes and bug fix > descriptions. > * in NEWS, i would put, for each release, the most crucial things, that > justify a new release > > Vincent > > > On Sat, 2009-01-31 at 22:16 +0100, Vincent Torri wrote: > >> > >> On Sat, 31 Jan 2009, Andrew Williams wrote: > >> > >>> You can of course have both. > >>> Generate a ChangeLog file from the subversion logs and have a subversion > >>> hook update this everytime a change is made... > >>> Would that keep everyone happy? > >> > >> not really (for me). The svn log would pollute the ChangeLog file with > >> useless commits like a warning fix. Do that with eet (which is tiny...), > >> and you'll see what I mean. > >> > >> Seriously, when an important commit must be noted in the ChangeLog (and > >> it should not happen a lot when the lib is released), it takes really no > >> time for the committer to use moap to update the ChangeLog file. I can't > >> understand why using a new tool is so disturbing for some people, and why > >> they are reluctant to use such new tool, especially when the commands are > >> so simple. > >> > >> Also I'm for using the right tool for the right task. svn log is not the > >> right tool, imho. > >> > >> Vincent > >> > >>> On 30 Jan 2009, at 19:23, Vincent Torri wrote: > >>> > >>>> > >>>> > >>>> On Fri, 30 Jan 2009, Gustavo Sverzut Barbieri wrote: > >>>> > >>>>> I really dislike ChangeLog files, they predate any source control > >>>>> version. Now CVS/SVN/Git/Whatever nicely replaces that. So generating > >>>>> it automatically is the way to go. > >>>> > >>>> of course I disagree. Mainly because of an experience i had with > >>>> autotools: for the EFL, I had to check if I didn't use macros that were > >>>> too recent, or on the contrary if they were old enough to replace them by > >>>> newer ones. If I had to look at all the svn logs, i doubt that i would > >>>> have finished that work today (there are a lot of macro / features in > >>>> autoconf, automake and libtool). > >>>> > >>>> On the contrary, I just opened the ChangeLog files, did a search in it, > >>>> and it was quite fast for me to find the informations. > >>>> > >>>> That's why I think that, if it helped me, a changeLog can help other > >>>> people. Note that I agree with raster's position here: noting in a > >>>> ChangeLog only the most important changes. For example, even if I had > >>>> committed in eet repo (only formatting and autotools stuff, iirc), i > >>>> didn't modified the ChangeLog (Well, actually, i added one entry, to > >>>> mention that the compilation can be done with Visual Studio). So the > >>>> ChangeLog does not grows too much and has only important cahnges in it. > >>>> > >>>> That's my opinion as a user of a tool. And i think that there are a lot > >>>> of users who don't know how to use cvs, svn or git and are quite happy to > >>>> have some ChangeLog files. > >>>> > >>>> Vincent > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> This SF.net email is sponsored by: > >>>> SourcForge Community > >>>> SourceForge wants to tell your story. > >>>> http://p.sf.net/sfu/sf-spreadtheword > >>>> _______________________________________________ > >>>> enlightenment-devel mailing list > >>>> enlightenment-devel@lists.sourceforge.net > >>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >>>> > >>> > >>> > >>> -- > >>> Ce message a été vérifié par MailScanner > >>> pour des virus ou des polluriels et rien de > >>> suspect n'a été trouvé. > >>> Message délivré par le serveur de messagerie de l'Université d'Evry. > >>> > >> ------------------------------------------------------------------------------ > >> This SF.net email is sponsored by: SourcForge Community SourceForge wants > >> to tell your story. http://p.sf.net/sfu/sf-spreadtheword > >> _______________________________________________ enlightenment-devel > >> mailing list enlightenment-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > -- > > Ce message a ?t? v?rifi? par MailScanner > > pour des virus ou des polluriels et rien de > > suspect n'a ?t? trouv?. > > Message d?livr? par le serveur de messagerie de l'Universit? d'Evry. > > > > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
