D 2.062 release

Jonathan M Davis jmdavisProg at gmx.com
Mon Feb 18 12:14:15 PST 2013


On Monday, February 18, 2013 18:43:37 Dmitry Olshansky wrote:
> 18-Feb-2013 17:22, Leandro Lucarella пишет:
> >> I also would love to see an automatically generated changelog
> >> similar to the original based on the bugzilla data. Can we add a
> >> "changelog description" field to bug reports so if the bug
> >> description (which arguably shouldn't be changed) isn't a very good
> >> changelog entry, that is used instead?
> > 
> > All we need to do is force people to update the changelog when making
> > a pull request. That's it. You are making everything more complex than
> > it should be...
> 
> Or instead somebody just has to take time and write down 10 most
> important things in new release. Add this task to release manager role.
> 
> *That's* what interesting not pushing more grunt work on contributors
> that basically doesn't work at all.
> 
> Other then this a small script to expand the bugzilla entries into a
> webpage (just like before title + link to bugzilla).

Exactly. It would be nice to have the list of bug fixes and whatnot listed on 
the page directly rather than linked to, but having that managed automatically 
is great. The real problem is that we need a set of "release notes" at the top 
which lists the important changes. That just means that someone needs to take 
the time to write that up for each release. Updating the changelog manually is 
not only broken because stuff gets missed, but it's broken because it causes 
merge problems if you merge in the changelog changes at the same time as the 
commit. We don't need all of that extra grunt work. We just need the release 
notes section to be written by someone (or someones) in preparation for the 
release.

- Jonathan M Davis


More information about the Digitalmars-d-announce mailing list