From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: html-mode demanding <html> a bit too tight
Date: Fri, 27 Apr 2007 16:08:26 +0300 [thread overview]
Message-ID: <ud51qyng5.fsf@gnu.org> (raw)
In-Reply-To: <85tzv2xrnh.fsf@lola.goethe.zz> (message from David Kastrup on Fri, 27 Apr 2007 08:22:58 +0200)
> From: David Kastrup <dak@gnu.org>
> Date: Fri, 27 Apr 2007 08:22:58 +0200
> Cc: Glenn Morris <rgm@gnu.org>, user42@zip.com.au, emacs-devel@gnu.org
>
> You may be basking in the illusion that this increases the quality of
> the released Emacs. I severely doubt that.
Actually, I'm positive that the quality of Emacs codebase has not
improved, on the average, for quite some time. We are in a limit
cycle, whereby changes are committed that could wait until after the
release, those changes cause breakage, the breakage is fixed, then
another unnecessary change is made, and so on. And the quality
respectively oscillates up and down, with no visible trend.
The only way to ensure that the pretest steadily improves the quality
is to consistently enforce more and more stringent rules as to what
changes can go in, until eventually the only allowed changes are
trivial doc fixes and simple rewording in the manuals--and then stick
to this stringent policy for a couple of last pretests.
By contrast, it seems that what we do is waiting for a long enough
period without bug reports as some kind of signal that ``there are no
more serious bugs''. This is of course false, since a period of
silence can (and usually will) be caused by something utterly
unrelated, such as a public holiday or college vacation. Such
decision policy simply means that we will release at some random point
in time, and the quality of the released Emacs will be similarly
random. (Yes, this is a straw man, but if someone can provide any
other reasonable rationale for the current decision policy, please be
my guest.)
next prev parent reply other threads:[~2007-04-27 13:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87647ooxwm.fsf@zip.com.au>
[not found] ` <jwvps5vry60.fsf-monnier+emacs@gnu.org>
[not found] ` <462CC030.8030203@gmail.com>
[not found] ` <87mz0y8vyk.fsf@zip.com.au>
2007-04-25 14:51 ` html-mode demanding <html> a bit too tight Richard Stallman
2007-04-25 17:36 ` Stefan Monnier
2007-04-25 18:18 ` Lennart Borgman (gmail)
2007-04-27 5:59 ` Richard Stallman
2007-04-26 4:11 ` Glenn Morris
2007-04-27 5:59 ` Richard Stallman
2007-04-27 6:22 ` David Kastrup
2007-04-27 13:08 ` Eli Zaretskii [this message]
2007-04-27 10:27 ` Kim F. Storm
2007-04-27 11:14 ` Lennart Borgman (gmail)
2007-04-27 11:41 ` David Kastrup
2007-04-27 11:49 ` Lennart Borgman (gmail)
2007-04-27 11:56 ` David Kastrup
2007-04-27 12:03 ` Lennart Borgman (gmail)
2007-04-27 12:22 ` David Kastrup
2007-04-27 21:41 ` Lennart Borgman (gmail)
2007-04-27 12:48 ` Eli Zaretskii
2007-04-27 14:11 ` David Reitter
2007-04-27 20:17 ` Lennart Borgman (gmail)
2007-04-27 20:53 ` Chong Yidong
2007-04-27 21:02 ` Lennart Borgman (gmail)
2007-04-27 18:58 ` Edward O'Connor
2007-04-27 12:53 ` Eli Zaretskii
2007-04-27 20:53 ` Kim F. Storm
2007-04-28 4:06 ` Richard Stallman
2007-04-28 13:59 ` David Kastrup
2007-04-28 14:20 ` Juanma Barranquero
2007-04-29 21:17 ` Kim F. Storm
2007-04-30 22:09 ` Richard Stallman
2007-05-04 9:13 ` unicode-2 and multitty (was: html-mode demanding <html> a bit too tight) David Kastrup
2007-05-04 9:41 ` unicode-2 and multitty Jason Rumney
2007-05-04 10:14 ` David Kastrup
2007-05-04 20:46 ` Kim F. Storm
2007-05-05 0:26 ` David Kastrup
2007-05-05 21:54 ` Stefan Monnier
2007-05-07 9:55 ` Kim F. Storm
2007-05-07 10:09 ` David Kastrup
2007-05-04 9:42 ` Ulrich Mueller
2007-05-04 10:39 ` unicode-2 and multitty (was: html-mode demanding <html> a bit too tight) Eli Zaretskii
2007-05-04 11:12 ` unicode-2 and multitty David Kastrup
2007-05-04 21:18 ` unicode-2 and multitty (was: html-mode demanding <html> a bit too tight) Richard Stallman
2007-05-05 0:17 ` unicode-2 and multitty David Kastrup
2007-04-27 11:17 ` html-mode demanding <html> a bit too tight Leo
2007-04-27 19:51 ` Glenn Morris
2007-04-28 4:07 ` Richard Stallman
2007-04-28 8:04 ` 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
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=ud51qyng5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).