Release notes for future versions

Gervase Markham gerv at
Fri Jan 16 10:49:36 UTC 2015


On 15/01/15 18:26, Mark Côté wrote:
> dkl has been chugging away at the release notes for 5.0rc1.  I would
> like to remind all developers, reviewers, and approvers that any
> significant change should be tagged with the "relnote" keyword.  Trying
> to figure out what should go into the release notes is very tedious when
> the keyword is regularly neglected.
> Second, I'd like to propose an amendment to this process: rather than

Can I counter-propose a different amendment?

We should keep the release notes in the docs/ folder as reST, and
require the patch to contain a patch to the release notes if it's
release-noteworthy. This means all the work is done at the time of patch
submission. The release manager has the option of trimming down the list
(and so we can err on the side of inclusion when considering whether
bugs are note-worthy), but won't need to go and seek information to add
it. So it would make their job easier.


More information about the developers mailing list