Re: [E-devel] eet and updating ChangeLog: the moap tool
On Sat, 31 Jan 2009 22:30:53 +0100 (CET) Vincent Torri 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 -
Re: [E-devel] eet and updating ChangeLog: the moap tool
On Sat, 31 Jan 2009 21:03:48 + Andrew Williams said: > 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? i'd have no problem with this. as for 1.0 for stuff (and 0.17.0 for e17) i would like to keep good changelogs kept - as when a release *IS* made then the changelog is already up to date for the release tarball. > Andy > > 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 > > > > > -- > 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 > -- - 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
Re: [E-devel] eet and updating ChangeLog: the moap tool
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. -- 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
Re: [E-devel] eet and updating ChangeLog: the moap tool
On Friday, 30 January 2009, at 15:41:35 (+0100), Vincent Torri wrote: > cedric just fixed a bug in eet, and he forgot to update the ChangeLog. I > do not criticise, it can happen to everyone, including me (and it did > happen to me). > > But, as we plan to do more releases, the ChangeLog will have to always be > updated when such fixes are done, and i think that we should take the > habit of updating the ChangeLog files with some tools that could help us. > > The gstreamer team uses a tool named 'moap' [1] (written by the previous > release manager of gstreamer, btw). I use it for epdf, edvi, eps and evil, > and it is quite nice regarding ChangeLog updates. > > To use it, go to the toplevel directory of the project, then: > > 1) run: > > moap cl prep > > this step modify the ChangeLog according to the modified files > > 2) Update the ChangeLog to add comments > > 3) run > > moap cl ci > > to commit the changes > > Note that i don't want that everyone use that tool and update always the > ChangeLog files right now. I just want to mention one of the features of > that tool, which can help us a lot when we will have to update the > ChangeLog files in the released EFL. > > Finally, last remark: unfortunately, the order of the changes in the > ChangeLog of eet is the reverse of the one that moap uses (currently, last > cahnges are at the bottom, while moap put them at the top of the > ChangeLog). Maybe we can modify the current ChangeLog and use maop for the > updates The "mzput" utility that comes with Mezzanine opens an editor pre-populated with date, time, and committer name and userid, aborts commits with empty change entries, and auto-appends messages to the Changelog as well as supplying them to the underlying SCM commit (though there is an option to suppress the append). And it maintains the Changelog in chronological order just like the project standard. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) --- "I don't think 'huge machine' is the right phrase to describe a cluster of 486/SX's. Maybe 'cluster-f***ed'..."-- Jacob Wilkins -- 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
Re: [E-devel] eet and updating ChangeLog: the moap tool
On Sat, 31 Jan 2009, 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. examples from svn log in eet: "endianess bugzors!" "Bilious barnacles" "fix the bitch" "update" "oops..." "sssh" "Silence" etc... if everyone would have done good ChangeLog entry from the beginning, why not, but it's not the case. I would be ashamed to propose a ChangeLog with such entries. 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. especially when some guys here don't hesitate to use big tools like valgrind, gdb, oprofile, write powerful shell scripts, use python and are very good programmers in general. Just 2 little lines are really a big challenge, it seems. Vincent 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. -- 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
Re: [E-devel] eet and updating ChangeLog: the moap tool
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. 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 -- 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
Re: [E-devel] eet and updating ChangeLog: the moap tool
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
Re: [E-devel] eet and updating ChangeLog: the moap tool
On Sat, 2009-01-31 at 21:03 +, 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? > > Andy I believe this should be done for all projects that are currently in svn. Besides having a filled out ChangeLog, it saved time when needing to do `svn log` (simply because the ChangeLog is already there) > > 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 > > > > > -- > 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 -- 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
Re: [E-devel] eet and updating ChangeLog: the moap tool
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? Andy 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 > -- 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
Re: [E-devel] eet and updating ChangeLog: the moap tool
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
Re: [E-devel] eet and updating ChangeLog: the moap tool
On Fri, Jan 30, 2009 at 12:41 PM, Vincent Torri wrote: > > Hey, > > cedric just fixed a bug in eet, and he forgot to update the ChangeLog. I > do not criticise, it can happen to everyone, including me (and it did > happen to me). > > But, as we plan to do more releases, the ChangeLog will have to always be > updated when such fixes are done, and i think that we should take the > habit of updating the ChangeLog files with some tools that could help us. > > The gstreamer team uses a tool named 'moap' [1] (written by the previous > release manager of gstreamer, btw). I use it for epdf, edvi, eps and evil, > and it is quite nice regarding ChangeLog updates. > > To use it, go to the toplevel directory of the project, then: > > 1) run: > > moap cl prep > > this step modify the ChangeLog according to the modified files > > 2) Update the ChangeLog to add comments > > 3) run > > moap cl ci > > to commit the changes > > Note that i don't want that everyone use that tool and update always the > ChangeLog files right now. I just want to mention one of the features of > that tool, which can help us a lot when we will have to update the > ChangeLog files in the released EFL. > > Finally, last remark: unfortunately, the order of the changes in the > ChangeLog of eet is the reverse of the one that moap uses (currently, last > cahnges are at the bottom, while moap put them at the top of the > ChangeLog). Maybe we can modify the current ChangeLog and use maop for the > updates 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. AFAIK changelogs are supposed to be the reverse order, like maop does, so changing to it is becoming more standard. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 -- 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
[E-devel] eet and updating ChangeLog: the moap tool
Hey, cedric just fixed a bug in eet, and he forgot to update the ChangeLog. I do not criticise, it can happen to everyone, including me (and it did happen to me). But, as we plan to do more releases, the ChangeLog will have to always be updated when such fixes are done, and i think that we should take the habit of updating the ChangeLog files with some tools that could help us. The gstreamer team uses a tool named 'moap' [1] (written by the previous release manager of gstreamer, btw). I use it for epdf, edvi, eps and evil, and it is quite nice regarding ChangeLog updates. To use it, go to the toplevel directory of the project, then: 1) run: moap cl prep this step modify the ChangeLog according to the modified files 2) Update the ChangeLog to add comments 3) run moap cl ci to commit the changes Note that i don't want that everyone use that tool and update always the ChangeLog files right now. I just want to mention one of the features of that tool, which can help us a lot when we will have to update the ChangeLog files in the released EFL. Finally, last remark: unfortunately, the order of the changes in the ChangeLog of eet is the reverse of the one that moap uses (currently, last cahnges are at the bottom, while moap put them at the top of the ChangeLog). Maybe we can modify the current ChangeLog and use maop for the updates Vincent [1] http://thomas.apestaart.org/moap/trac -- 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
