unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Branch freezing for release
Date: Wed, 10 Apr 2019 21:26:32 +0300	[thread overview]
Message-ID: <83lg0h67jb.fsf@gnu.org> (raw)
In-Reply-To: <jwv1s29u4mo.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 10 Apr 2019 13:56:06 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Wed, 10 Apr 2019 13:56:06 -0400
> 
> > Nothing's changed, the status is still according to CONTRIBUTE: the
> > next release is 26.2, i.e. the minor version is > 1, so only doc fixes
> > are automatically safe; the rest should get an explicit permission,
> > and generally they won't get it (since we already had RC1).
> 
> What about bug-fixes for 26.3?

We can talk about that once Emacs 26.2 is out.



  reply	other threads:[~2019-04-10 18:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871s3jeh8m.fsf@ericabrahamsen.net>
     [not found] ` <handler.34776.B.155191354931988.ack@debbugs.gnu.org>
     [not found]   ` <87zhq4zzcz.fsf@ericabrahamsen.net>
     [not found]     ` <t0sgvwls0r.fsf@fencepost.gnu.org>
     [not found]       ` <871s3a90qo.fsf@ericabrahamsen.net>
     [not found]         ` <87imvmbube.fsf@gmail.com>
     [not found]           ` <i036mqtu61.fsf@fencepost.gnu.org>
     [not found]             ` <D34DE67E-9443-43B5-8771-B332C5A08637@gnu.org>
     [not found]               ` <87mukyiczg.fsf@ericabrahamsen.net>
     [not found]                 ` <AC8095A5-8058-4301-87CE-209F699F0955@gnu.org>
     [not found]                   ` <877ec2iau1.fsf@ericabrahamsen.net>
     [not found]                     ` <4CAA6D9F-0402-489C-8DD1-CE2ADBAA42C9@gnu.org>
2019-04-10  8:57                       ` Branch freezing for release (WAS: bug#34776) Noam Postavsky
2019-04-10  9:21                         ` Eli Zaretskii
2019-04-10 16:16                           ` Noam Postavsky
2019-04-10 16:40                             ` Eli Zaretskii
2019-04-10 16:59                               ` Branch freezing for release Basil L. Contovounesios
2019-04-10 17:12                                 ` Eli Zaretskii
2019-04-10 17:39                                   ` Basil L. Contovounesios
2019-04-10 18:31                                     ` Eli Zaretskii
2019-04-11 14:02                                       ` Basil L. Contovounesios
2019-04-22 13:03                                       ` Basil L. Contovounesios
2019-04-22 13:14                                         ` Eli Zaretskii
2019-04-22 15:18                                           ` Basil L. Contovounesios
2019-04-10 17:56                                   ` Stefan Monnier
2019-04-10 18:26                                     ` Eli Zaretskii [this message]
2019-04-10 18:54                                       ` Stefan Monnier
2019-04-10 19:19                                         ` Eli Zaretskii
2019-04-10 20:16                                           ` Dmitry Gutov
2019-04-11  0:12                                             ` Noam Postavsky
2019-04-11 13:52                                               ` Eli Zaretskii
2019-04-12  1:03                                                 ` Noam Postavsky
2019-04-12  7:04                                                   ` Eli Zaretskii
2019-04-12 10:18                                                     ` Noam Postavsky
2019-04-12 12:23                                                       ` Stefan Monnier
2019-04-12 12:24                                                       ` Eli Zaretskii
2019-04-12 14:14                                                     ` Dmitry Gutov
2019-04-10 13:14                         ` Stefan Monnier
2019-04-10 13:47                           ` Andreas Schwab
2019-04-10 15:03                           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lg0h67jb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).