From: Michael Albinus <michael.albinus@gmx.de>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Eli Zaretskii <eliz@gnu.org>, John Wiegley <johnw@gnu.org>,
Nicolas Petton <nicolas@petton.fr>,
Emacs-devel <emacs-devel-bounces+psainty=orcon.net.nz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Releasing Emacs 26.1
Date: Mon, 07 May 2018 13:29:39 +0200 [thread overview]
Message-ID: <878t8vhffg.fsf@gmx.de> (raw)
In-Reply-To: <3e95f4268aef910f3d18165a737ff8d2@webmail.orcon.net.nz> (Phil Sainty's message of "Mon, 07 May 2018 23:10:57 +1200")
Phil Sainty <psainty@orcon.net.nz> writes:
Hi Phil,
> If the bugs are in new functionality, I wouldn't see any issue with
> leaving the improvements until the next release if necessary; but
> I would have thought known regressions to behaviour which was working
> properly in the previous stable release would be worth delaying the
> new release to fix, if necessary.
>
> I suppose I don't understand why there's any hurry to release 26.1.
Because it wouldn't be released ever, otherwise. The Emacs bug tracker
contains 1742 open bugs in state "serious,important,normal" as of
today. I bet there are many open bugs we could apply the same reasoning
as you have given above.
Emacs 26.1 is in code-freeze. Bug#31355 does not block Emacs 26.1, and a
workaround (your patch) does exist. So I don't believe this bug shall
stop the release.
But I'm neither the maintainer nor the release manager, which will
decide. Eli? John? Nico?
> -Phil
Best regards, Michael.
next prev parent reply other threads:[~2018-05-07 11:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 19:52 Releasing Emacs 26.1 Eli Zaretskii
2018-05-06 21:00 ` Alan Third
2018-05-07 1:21 ` Basil L. Contovounesios
2018-05-07 12:31 ` Alan Third
2018-05-07 12:46 ` Basil L. Contovounesios
2018-05-07 17:42 ` Eli Zaretskii
2018-05-07 0:13 ` Phil Sainty
2018-05-07 7:32 ` Michael Albinus
2018-05-07 11:10 ` Phil Sainty
2018-05-07 11:29 ` Michael Albinus [this message]
2018-05-07 15:08 ` Nicolas Petton
2018-05-07 18:09 ` Eli Zaretskii
2018-05-07 11:44 ` Van L
2018-05-07 12:05 ` Bastien
2018-05-07 18:08 ` Eli Zaretskii
2018-05-07 17:44 ` Eli Zaretskii
2018-05-07 5:30 ` John Wiegley
2018-05-07 5:40 ` Bastien
2018-05-07 19:05 ` Eli Zaretskii
2018-05-07 22:06 ` Rasmus
2018-05-08 2:28 ` Eli Zaretskii
2018-05-08 7:06 ` Byung-Hee HWANG (황병희, 黃炳熙)
2018-05-20 13:56 ` Alan Mackenzie
2018-05-20 15:48 ` Eli Zaretskii
2018-05-20 19:14 ` Alan Mackenzie
2018-05-21 9:25 ` Nicolas Petton
2018-05-22 7:38 ` Tino Calancha
2018-05-22 9:40 ` Van L
2018-05-22 9:56 ` Van L
2018-05-24 1:40 ` Van L
2018-05-25 5:10 ` Tino Calancha
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=878t8vhffg.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel-bounces+psainty=orcon.net.nz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=nicolas@petton.fr \
--cc=psainty@orcon.net.nz \
/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).