From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>, Eli Zaretskii <eliz@gnu.org>,
p.stephani2@gmail.com, emacs-devel <emacs-devel@gnu.org>,
nilsb@google.com
Subject: Re: Making better use of the "release blocking list" [was: bug#23288: 25.0.92; Clicking on links inserts primary X selection]
Date: Thu, 12 May 2016 14:43:40 -0700 [thread overview]
Message-ID: <33d66ff1-7bf2-2ba5-29d9-b510bf1e344e@cs.ucla.edu> (raw)
In-Reply-To: <m2bn4b2nv0.fsf_-_@newartisans.com>
On 05/12/2016 10:21 AM, John Wiegley wrote:
> I only introduced a date to focus our decision making around 25.1, and
> since
> this is what I'm used to doing to ship software.
>
> HOWEVER, if having a date is stressful or unpleasant for those doing the work,
> we can get rid of it.
The date is arbitrary and should not be driving development. That being
said, the list of blocking bugs is too long: currently 28 entries, and
they are largely nontrivial. The list needs to be whittled down.
> I don't mind if Emacs 25 takes another year to happen
I would mind. Two years between releases is too long. This isn't gzip
we're talking about.
next prev parent reply other threads:[~2016-05-12 21:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 12:31 bug#23288: 25.0.92; Clicking on links inserts primary X selection Philipp Stephani
2016-04-14 15:33 ` Glenn Morris
2016-04-14 17:14 ` Nils Berg
2016-04-16 13:36 ` Philipp Stephani
2016-04-18 8:50 ` Nils Berg
2016-04-20 16:53 ` Philipp Stephani
2016-05-10 21:25 ` Philipp Stephani
2016-05-11 8:14 ` Eli Zaretskii
2016-05-11 8:32 ` Nils Berg
2016-05-11 13:01 ` Philipp Stephani
2016-05-11 13:14 ` Nils Berg
2016-05-11 13:32 ` Philipp Stephani
2016-05-11 13:56 ` Eli Zaretskii
2016-05-11 18:18 ` John Wiegley
2016-05-11 18:40 ` Glenn Morris
2016-05-11 21:04 ` Eli Zaretskii
2016-05-12 5:42 ` John Wiegley
2016-05-12 19:26 ` Eli Zaretskii
2016-05-12 21:24 ` John Wiegley
2016-05-12 16:49 ` Glenn Morris
2016-05-12 17:21 ` Making better use of the "release blocking list" [was: bug#23288: 25.0.92; Clicking on links inserts primary X selection] John Wiegley
2016-05-12 21:43 ` Paul Eggert [this message]
2016-05-16 19:08 ` Glenn Morris
2016-05-18 6:09 ` John Wiegley
2016-05-21 19:06 ` Eli Zaretskii
2016-05-21 20:48 ` Mike Kupfer
2016-05-23 4:58 ` Bill Wohler
2016-05-30 23:21 ` Bill Wohler
2016-05-22 2:02 ` Paul Eggert
2016-05-22 4:52 ` John Wiegley
2016-05-22 16:38 ` Eli Zaretskii
2016-05-22 16:31 ` Eli Zaretskii
2016-05-22 21:09 ` Dmitry Gutov
2016-05-22 21:24 ` Dmitry Gutov
2016-05-23 2:32 ` Eli Zaretskii
2016-05-23 13:18 ` Dmitry Gutov
2016-05-23 16:15 ` Paul Eggert
2016-05-23 16:36 ` Dmitry Gutov
2016-05-23 17:39 ` Paul Eggert
2016-05-23 16:52 ` Eli Zaretskii
2016-05-13 9:02 ` Eli Zaretskii
2016-05-13 16:36 ` John Wiegley
2016-05-20 18:24 ` bug#23288: 25.0.92; Clicking on links inserts primary X selection Philipp Stephani
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=33d66ff1-7bf2-2ba5-29d9-b510bf1e344e@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nilsb@google.com \
--cc=p.stephani2@gmail.com \
--cc=rgm@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.