Using releasenotes extension for 4.4 cycle

Kevin Bullock kbullock+mercurial at ringworld.org
Mon Jul 24 14:37:19 EDT 2017


> On Jul 24, 2017, at 10:41, Yuya Nishihara <yuya at tcha.org> wrote:
> 
> On Sun, 23 Jul 2017 11:39:21 -0700, Gregory Szorc wrote:
>> Rishabh has been doing great work on the releasenotes extension.
>> 
>> I'd like to start using it as part of developing Mercurial itself. And the
>> sooner we do that, the sooner we'll flush out bugs, pain points, etc.
>> 
>> I'd like to propose attempting to use the releasenotes extension for the
>> duration of the 4.4 cycle. I imagine this entails the following:
> 
> Sounds fine.

Agreed, I'm excited to start using it!

>> * Bike shedding on the sections/admonitions to use for Mercurial itself
>> (the default sections in the extension today might be good enough because
>> they were modeled after Mercurial)

Yeah, I think we can start with the default admonitions. If we find anything lacking, we can always add it later.

>> * Encouraging patch authors to include admonitions in commit messages
>> * Encouraging reviewers to add admonitions to commit messages when commits
>> are queued
> 
> Can I expect native reviewers will rewrite that part? It could be a high
> barrier for non-natives to send/queue patches.

Yes, I'm happy to copy-edit release notes (I would do so when cutting a release at the least).

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock



More information about the Mercurial-devel mailing list