From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: lekktu@gmail.com, cyd@stupidchicken.com, emacs-devel@gnu.org,
storm@cua.dk, eliz@gnu.org
Subject: Re: Release schedule
Date: Mon, 23 Apr 2007 01:13:47 -0400 [thread overview]
Message-ID: <jwvhcr765gm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1HfpX0-0002jI-4w@fencepost.gnu.org> (Richard Stallman's message of "Sun\, 22 Apr 2007 23\:48\:02 -0400")
> If only we'd manage to get a pretest cycle finished without somebody
> noticing things that "really need to" get reorganized before the
> release.
> It is a good thing someone noticed!
It's not. I can easily come up with "something that needs reorganizing" or
even with plain bugs. I don't know how long I could keep it up, but I'm
pretty sure I could delay the release by a few years this way.
Emacs is and has always be "approximate", allowing itself incorrect
behaviors in various "corner" cases, based on the expectation that the user
will notice it. The result is "a big happy mess" that's also
tremendously useful. Fixing it would amount to breaking it.
Stefan
next prev parent reply other threads:[~2007-04-23 5:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 21:53 Release schedule Richard Stallman
2007-04-21 3:38 ` Chong Yidong
2007-04-21 10:11 ` Eli Zaretskii
2007-04-21 19:25 ` Chong Yidong
2007-04-21 20:02 ` Glenn Morris
2007-04-21 20:14 ` Chong Yidong
2007-04-21 20:17 ` Glenn Morris
2007-04-21 22:31 ` Nick Roberts
2007-04-21 23:02 ` Glenn Morris
2007-04-22 3:08 ` Eli Zaretskii
2007-04-22 8:11 ` Juanma Barranquero
2007-04-22 10:33 ` Kim F. Storm
2007-04-22 11:13 ` David Kastrup
2007-04-23 3:48 ` Richard Stallman
2007-04-23 5:13 ` Stefan Monnier [this message]
2007-04-23 6:12 ` David Kastrup
2007-04-22 11:51 ` Romain Francoise
2007-04-22 14:20 ` Chong Yidong
2007-04-22 22:56 ` Kenichi Handa
2007-04-22 16:35 ` Richard Stallman
2007-04-22 20:42 ` Eli Zaretskii
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=jwvhcr765gm.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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.