[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Branch freezing for release

From: Basil L. Contovounesios
Subject: Re: Branch freezing for release
Date: Wed, 10 Apr 2019 17:59:14 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Noam Postavsky <address@hidden>
>> Date: Wed, 10 Apr 2019 12:16:35 -0400
>> Cc: Emacs developers <address@hidden>, Eric Abrahamsen <address@hidden>
>> > > 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.
> If just one of these two things happened -- either they asked whether
> it was okay to push, or the RC was pushed and tagged -- we'd be okay,
> but none of them happened.

Just to be clear: is it okay to push/backport fixes to emacs-26 again?
I've noted the following commits as candidates for backporting:

[1: 10cd65878c]: Update documentation for indent-relative functions
  2019-04-05 19:48:21 -0500

[2: 0e468a6204]: Avoid using obsolete indent-relative-maybe
  2019-04-03 17:55:40 +0100

[3: 690c678fb6]: Fix comment-empty-lines docstring (bug#35152)
  2019-04-04 23:41:02 +0100

N.B.: Commit [2] also includes small code changes, not just docfixes.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]