From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bozhidar@batsov.com, emacs-devel@gnu.org
Subject: Re: Very happy with emacs-25 so far
Date: Mon, 21 Mar 2016 10:52:09 -0700 [thread overview]
Message-ID: <m260wfvhva.fsf@newartisans.com> (raw)
In-Reply-To: <83k2kx7reo.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Mar 2016 05:35:27 +0200")
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> What is the purpose of marking them as blocking the release if we don't
> really mean that?
Marking a bug as blocking the release does not mean we won't release, because
this would put our release schedule in the hands of anyone capable of setting
such a mark.
What it does mean is: prior to cutting a release tarball, we will have
addressed each bug, where by "address" we mean:
1. Fix it, or
2. Defer it to 25.2, or
3. Re-categorize as not really blocking
It sounds like several of our current "blockers" should not have been marked
such, so it looks like a bug review is in order. I'll put it on my schedule to
go through these and see which ones truly should not ship in 25.1.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
next prev parent reply other threads:[~2016-03-21 17:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 23:28 Very happy with emacs-25 so far John Wiegley
2016-03-19 17:45 ` Bozhidar Batsov
2016-03-19 18:53 ` Eli Zaretskii
2016-03-19 23:09 ` John Wiegley
2016-03-20 3:35 ` Eli Zaretskii
2016-03-20 10:34 ` Lars Magne Ingebrigtsen
2016-03-20 16:23 ` Eli Zaretskii
2016-03-20 16:38 ` Bozhidar Batsov
2016-03-21 17:52 ` John Wiegley [this message]
2016-03-21 18:37 ` Eli Zaretskii
2016-03-21 21:15 ` John Wiegley
2016-03-21 22:22 ` Nicolas Petton
2016-03-21 22:38 ` Michael Heerdegen
2016-03-21 23:04 ` Paul Eggert
2016-03-22 3:31 ` Eli Zaretskii
2016-03-21 20:13 ` Paul Eggert
2016-03-22 0:14 ` Rostislav Svoboda
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m260wfvhva.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=bozhidar@batsov.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.