From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Release-critical bugs
Date: Wed, 17 Sep 2014 15:40:39 -0400 [thread overview]
Message-ID: <arvbomvxvs.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87mw9yb2f8.fsf@engster.org> (David Engster's message of "Wed, 17 Sep 2014 19:08:11 +0200")
David Engster wrote:
> What are the remaining bugs which are actually critical for 24.4?
Thanks for asking! :)
I'm not keeping particularly close track myself.
> #18182, for instance; can that be closed?).
I don't think it's fixed, but on the other hand I don't think
anything more is going to happen with it.
> Maybe we could mark the actually release-critical bugs as, say,
> 'critical', and maybe also list them here and discuss how to fix them?
Feel free to do that if you think it will help.
I think using severity in this way was a bit of a quick-and-dirty hack.
Maybe a usertag would have been better.
> Especially the GnuTLS stuff goes way over my head, I'm afraid.
And most people's I think. That's why these are long-term issues that
don't see much progress. It seems far too late to make any changes
related to GnuTLS for this release anyway. But nevertheless they remain
important issues (which is why using severity in this way is not great).
Of the important ones, the only ones I would like to see fixed are:
18334
18444
Neither is truly important, and both could be left unfixed at no great
loss for 24.4, but I think someone should at least have a go...
If there are other issues people would like to draw attention to, they
should do so here I guess.
This release is really dragging...
next prev parent reply other threads:[~2014-09-17 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 17:08 Release-critical bugs David Engster
2014-09-17 19:40 ` Glenn Morris [this message]
2014-09-18 2:16 ` Ivan Andrus
2014-09-18 17:28 ` Glenn Morris
2014-09-18 2:39 ` Eli Zaretskii
2014-09-18 12:57 ` Rasmus
2014-09-18 14:51 ` Eli Zaretskii
2014-09-18 17:28 ` Glenn Morris
2014-09-18 17:40 ` Eli Zaretskii
2014-09-19 16:49 ` Glenn Morris
2014-09-19 17:34 ` Eli Zaretskii
2014-09-24 13:48 ` Ted Zlatanov
2014-09-24 15:04 ` Stefan Monnier
2014-09-27 15:10 ` Jens Lechtenboerger
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=arvbomvxvs.fsf@fencepost.gnu.org \
--to=rgm@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.