On Fri, Sep 21, 2012 at 4:04 PM, Vincent Torri <vincent.to...@gmail.com> wrote: > On Fri, Sep 21, 2012 at 8:50 PM, Lucas De Marchi > <lucas.demar...@profusion.mobi> wrote: >> On Thu, Sep 20, 2012 at 8:26 PM, Carsten Haitzler <ras...@rasterman.com> >> wrote: >>> On Thu, 20 Sep 2012 23:43:36 +0200 Vincent Torri <vincent.to...@gmail.com> >>> said: >>> >>>> On Thu, Sep 20, 2012 at 7:53 PM, Lucas De Marchi >>>> <lucas.demar...@profusion.mobi> wrote: >>>> > On Thu, Sep 20, 2012 at 2:30 PM, Vincent Torri <vincent.to...@gmail.com> >>>> > wrote: >>>> >> On Thu, Sep 20, 2012 at 7:26 PM, Lucas De Marchi >>>> >> <lucas.demar...@profusion.mobi> wrote: >>>> >>> On Thu, Sep 20, 2012 at 2:20 PM, Vincent Torri >>>> >>> <vincent.to...@gmail.com> >>>> >>> wrote: >>>> >>>> On Thu, Sep 20, 2012 at 6:27 PM, Eduardo Lima (Etrunko) >>>> >>>> <ebl...@gmail.com> wrote: >>>> >>>>>>> that's what the commit message is for. When it does all >>>> >>>>>>> automatically, >>>> >>>>>>> then it's an option. >>>> >>>>>> >>>> >>>>>> did you look at the Evil's changeLog ? You'll see why the commit >>>> >>>>>> message is not sufficient >>>> >>>>>> >>>> >>>>> >>>> >>>>> If you are talking about the list of files changed, it is just plain >>>> >>>>> useless. There is a --verbose option of svn log that will also output >>>> >>>>> the changed files. >>>> >>>> >>>> >>>> you're stupid or what ? We are not talking about the content of a >>>> >>>> changelog but of its layout ! >>>> >>> >>>> >>> >>>> >>> It seems everybody except you agree the ChangeLog file is just plain >>>> >>> useless. >>>> >> >>>> >> ultra funny. It's just profusion guys who want to drop changelog >>>> > >>>> > Eduardo doesn't work here: >>>> > >>>> > Excerpt from the README file in libabc >>>> > (https://git.kernel.org/?p=linux/kernel/git/kay/libabc.git;a=blob;f=README;h=b4bed51b0403f0f55f4e8bb4706cd97e23c4858c;hb=HEAD): >>>> > >>>> > Update NEWS to let developers know what has changed >>>> > - It's the history of the project, stuff that packagers need to know >>>> > when putting a new version in the distro. The interesting changes >>>> > or added/removed functionality from version to version. This is >>>> > not a commit changelog. >>>> > - If you want to provide ChangeLog, use the one generated >>>> > by git, do not maintain your own. >>>> >>>> so what ? counter-example: >>>> >>>> http://www.gnu.org/prep/standards/html_node/Change-Logs.html >>>> >>>> > kernel doesn't use a ChangeLog file >>>> > systemd doesn't use a ChangeLog file >>>> > bluez doesn't use a ChangeLog file >>>> > connman doesn't use a ChangeLog file >>>> > kernel doesn't use a ChangeLog file >>>> > node doesn't use a ChangeLog file >>>> > go doesn't use a ChangeLog file >>>> > pulseaudio doesn't use a ChangeLog file >>>> > >>>> > v8 uses a ChangeLog file that's really a NEWS file >>>> > webkit uses a semi-automated ChangeLog file, creating the commit >>>> > message from the changelog. And it's stupid. Been there. >>>> >>>> and i'm sure i can find HUNDREDS of libs with changelog. I have as >>>> many arguments as you have. >>>> >>>> > And WE are back to 90's maintaining that stupid files ourselves >>>> >>>> to be clear : I don't like our NEWS file. For me: >>>> >>>> ChangeLog should contain exactly what its name means : log of changes. >>>> Not all of changes of course. >>>> >>>> NEWS means what's new : that is, entries for the release, API >>>> additions, deprecations, and eventually the mention of a big >>>> improvement or a fix of a really big bug. That is, all the >>>> improvements part should go away, as I agree that it duplicates what >>>> is in ChangeLog. raster and others add that part, i accepted it. But I >>>> don't like it. And that's not the only stuff that I don't like but >>>> that i have accpeted in that project. >>> >>> i agree with vincent here fyi. the actual git or svn or cvs or whatever log >>> is >>> footwork. it isn't publishable data beyond being useful for day-to-day >>> hunting >>> of who did what. >>> >>> changelog is "useful publishable changes" just in the order they are done. >> >> that is the purpose of NEWS > > http://www.gnu.org/prep/standards/html_node/NEWS-File.html#NEWS-File > http://www.gnu.org/prep/standards/html_node/Change-Logs.html > >> >> So we are maintaining the same thing, in 2 different places... NEWS >> and ChangeLog. It's just a change in format. > > no, they are different. There are much more in changelog than in NEWS. > >> If there's a new feature at release time it should be in NEWS file. It >> doesn't matter the date in which it was added. Not for whoever is >> packaging that stuff. > > what is important is the version in which the feature is added.
and that should be present in NEWS Lucas De Marchi ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel