From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Are we in feature-freeze?
Date: Sun, 28 Sep 2008 06:25:01 +0300 [thread overview]
Message-ID: <u4p41kl4i.fsf@gnu.org> (raw)
In-Reply-To: <87vdwh2cr8.fsf@cyd.mit.edu>
> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Sat, 27 Sep 2008 23:03:07 -0400
>
> Nick Roberts <nickrob@snap.net.nz> writes:
>
> > There are so many major things that need fixing for 23.1, that I think
> > it's counterproductive to put a freeze on minor features now, like the
> > one Eli is suggesting. A total freeze only seems appropriate when
> > bugs are being actively fixed, and I don't see that now.
>
> Bugs are being actively fixed. Not as quickly as I would like, since we
> don't have enough people working on it, but we are very much in the bug
> reduction phase.
Is FOR-RELEASE supposed to be the definitive list of things to be
fixed before the release, or are there some alternative methods
available now that we use a bug tracker?
If it's still FOR-RELEASE, then several problems people were
complaining about are not even there. For example, the slow redisplay
with the font back-ends, and the problems with non-ASCII characters on
TTYs. I don't think we can release Emacs with these two problems.
next prev parent reply other threads:[~2008-09-28 3:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 8:48 Are we in feature-freeze? Eli Zaretskii
2008-09-27 12:25 ` Stefan Monnier
2008-09-27 14:51 ` Eli Zaretskii
2008-09-27 19:50 ` Chong Yidong
2008-09-27 23:27 ` Nick Roberts
2008-09-28 3:03 ` Chong Yidong
2008-09-28 3:25 ` Eli Zaretskii [this message]
2008-09-28 5:13 ` Chong Yidong
2008-09-28 7:22 ` Nick Roberts
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=u4p41kl4i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).