From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: bozhidar@batsov.com, emacs-devel@gnu.org
Subject: Re: Very happy with emacs-25 so far
Date: Sun, 20 Mar 2016 05:35:27 +0200 [thread overview]
Message-ID: <83k2kx7reo.fsf@gnu.org> (raw)
In-Reply-To: <m2oaaaxdy3.fsf@newartisans.com> (message from John Wiegley on Sat, 19 Mar 2016 16:09:24 -0700)
> From: John Wiegley <jwiegley@gmail.com>
> Cc: Bozhidar Batsov <bozhidar@batsov.com>, emacs-devel@gnu.org
> Date: Sat, 19 Mar 2016 16:09:24 -0700
>
> >> Do we have some ETA on the final release?
>
> > We won't have one, until we see some serious pouncing on bugs mentioned in
> > bug#19759, with the purpose of either fixing them, or deciding that they
> > shouldn't block the release.
>
> Yes, I do have one: June 21. Nor am I willing to wait forever. If we arrive at
> the summer and there are still a few outstanding issues, we may simply note
> them in the release document, and make it an incentive to quickly release 25.2
> afterward.
What is the purpose of marking them as blocking the release if we
don't really mean that?
next prev parent reply other threads:[~2016-03-20 3:35 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 [this message]
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
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
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=83k2kx7reo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bozhidar@batsov.com \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
/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).