[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stable 2.16 releases (dictator)
From: |
Graham Percival |
Subject: |
Re: Stable 2.16 releases (dictator) |
Date: |
Mon, 16 Jul 2012 07:11:28 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sat, Jul 14, 2012 at 10:30:49AM +0200, David Kastrup wrote:
> Graham Percival <address@hidden> writes:
>
> > The policy is: David Kastrup has sole authority over what goes
> > into stable/2.16 and which release(s) will have a version number
> > of 2.16.x, until 2012 Dec 31.
>
> Or until he asks to relinquish control, or there is sufficient agreement
> among core developers that he should.
I've added "if he quits, we have a new discussion" to the list.
> Being able to look at a list of Critical issues is useful to make sure
> no oversights happen. So I'd propose that we use the same rules as
> before for marking issues as Critical (in particular, letting a
> regression automatically imply a Critical issue), but that I have the
> leeway of downmarking and/or ignoring them.
Changed accordingly.
> > - translators do not merge or cherry-pick onto stable/2.16
> > unless specifically requested to do so.
>
> So nobody should cherry-pick or merge
> _from_ this branch either, in particular not into the mainline, since
> release-specific fixes might be unsuitable for the development branch.
Added, thanks.
- Graham