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 14:15:49 -0700 [thread overview]
Message-ID: <m28u1bsfay.fsf@newartisans.com> (raw)
In-Reply-To: <83d1qn65j8.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 21 Mar 2016 20:37:47 +0200")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> Fixing bugs might not be a 1-sec job, to say nothing of the need to test the
> fixed version in yet another pretest. So I wouldn't recommend delaying that
> till just before the release.
I think we're just miscommunicating due to the lovely nature of e-mail. By
'prior to release' I just meant "in the time before release happens", which
could be much sooner than 1 second before. :)
I give you extra-special cookie points for every bug you fix in one second,
though.
>> 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.
> That's exactly my point: we should decide _today_ which one are truly
> blocking, and then make all the necessary effort, starting with tomorrow, to
> fix those which are.
Ok, can we say "decide by Friday" so that I don't curl up from stress and
implode into an x-ray emitting, black hole of worry on my office chair? I'm
almost done being sick from last week, which has weakened my resolve to
"carpe diem" today.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-03-21 21:15 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
2016-03-21 18:37 ` Eli Zaretskii
2016-03-21 21:15 ` John Wiegley [this message]
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=m28u1bsfay.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 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).