Re: Branch freezing for release (WAS: bug#34776)

[Noam Postavsky]

On Wed, 10 Apr 2019 at 05:21, Eli Zaretskii <address@hidden> wrote:

> > >>>>>> The RC said Emacs 26.2 was to be released March 27...  Part of
> > >>>>>> making a release is for people to stop changing that branch.
> > >>>>>
> > >>>>> Unfortunately, that ship has sailed, since within an hour of RC
> > >>>>> release a new commit was pushed to the release branch [...]

> > CONTRIBUTE says:
> >
> > Doc fixes are always considered "safe" -- even when a release branch
> > is in feature freeze, it can still receive doc fixes.
> >
> > I don't see anything there about not pushing after an RC is made

> There's no need to say anything else, since an RC should be tarred after all 
> its changes are pushed and tagged.  That didn't happen this time by omission. 
>  We all make mistakes at times.

Ah, I had initially thought you meant the unfortunate mistake was on
part of the person/people pushing to emacs-26 after the RC. Makes more
sense this way.