Re: Branch freezing for release

[Dmitry Gutov <dgutov@yandex.ru>]

On 12.04.2019 10:04, Eli Zaretskii wrote:

>>> If someone can suggest a better way of saying that, please do.  The
>>> text does say soon afterwards "if you are unsure, ask".
>>
>> Maybe it helps to spell out a number?
> 
> I'd hesitate to fix the number at 90 (or any other specific number),
> because sometimes .90 is not close enough.  We could say .100, but
> AFAIR that happened only once or twice in the history, so it would not
> be helpful.  The problem here is that the number is not determined by
> how close we think we are to the release, its correlation with that is
> very weak.

A bit arbitrary, but OK.

Instead, though, we could say something like: "you are allowed to commit 
to branches named emacs-xy basically anything except huge new features, 
but branches named emacs-xy.z are special, and you should only commit 
there if you know you can, and ask if you're unsure".

This kind of release branching should be familiar to many. I've read 
about it being used for Firefox, for example, several years ago.