[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [groff] Savannah bug field usage protocol
From: |
Colin Watson |
Subject: |
Re: [groff] Savannah bug field usage protocol |
Date: |
Sun, 22 Apr 2018 11:29:39 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Sat, Apr 21, 2018 at 05:43:12PM -0400, G. Branden Robinson wrote:
> At 2018-04-21T14:21:03+0100, Ralph Corderoy wrote:
> > Some projects maintain a `pending' release notes so that significant
> > fixes and changes get added to as they're implemented. This might avoid
> > the need to keep some bugs non-closed until the release. Come release,
> > the file's reviewed, some minor things with highsight ditched, and the
> > commit log scanned for anything missing.
>
> Our commit discipline is already supposed to include updating the
> ChangeLog, and, where appropriate, NEWS files as part of the commit
> where the underlying change is made. Do you think that should suffice
> for aiding the preparation of Release Notes?
I agree with the sentiment, but do the ~40 lines of NEWS entries since
1.22.3 really reflect the ~1900 lines of ChangeLog for the same period?
I'm not really qualified to prepare updates there, but the ratio seems
unusually low to me.
--
Colin Watson address@hidden