unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: rms@gnu.org
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: [Stephen.Berman@gmx.net: Re: redisplay]
Date: Mon, 30 Apr 2007 00:14:12 +0200	[thread overview]
Message-ID: <85647ebzgr.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1HiH8q-0006kl-1L@fencepost.gnu.org> (Richard Stallman's message of "Sun\, 29 Apr 2007 17\:41\:12 -0400")

Richard Stallman <rms@gnu.org> writes:

>     I see a gross flaw in installing "almost certain improvements"
>     in a central area of Emacs when we are trying to pin down a
>     final release.
>
> The improvement in question consists of at least partly fixing a bug.

You don't understand what prerelease testing is about.  The goal is
not to get a bugfree version of Emacs released.  Whoever thinks this
possible is lunatic.  The goal is to release a version of Emacs which
has not introduced severe regressions in a time frame where they could
have escaped noticing.

Every change, including bug fixes, in particular in general areas,
carries with it the danger of introducing _exactly_ those kind of
heavy regressions.  The ChangeLog files are _full_ of reverted fixes
which turned out to do something wrong.

If we go on fixing bugs that are not a direct consequence of very
recent changes, we will never get to the state where we can be sure
not to have release-critical bugs introduced without notice.

The bugs you found necessary fixing in the last few weeks are _much_
_much_ more harmless than having to use Emacs 21 instead of Emacs 22.

Emacs 22 will _never_ be in a bugfree state before the release.  Nor
will it become bugfree afterwards.  But at least afterwards we can
make overall progress.

In contrast to the problem of the delayed release, you are playing
with toy problems.  Problems that will pop up for years and years to
come.

It is not sane to delay the release because of that: a release is
appropriate when there is a definite improvement over the last release
without major regressions.  This has been the case for years,
actually.  There is no sense in instead of improvement demanding
perfection.  People experienced with software releases have told you
this time and again.  You chose to scorn them for their frustration
about you ignoring established procedures and conventional wisdom.

Do you really not see what you are doing?  For how long are you going
to sabotage the attempts of the developers to get Emacs 22.1 released?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-04-29 22:14 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23  3:48 [Stephen.Berman@gmx.net: Re: redisplay] Richard Stallman
2007-04-23 15:07 ` Chong Yidong
2007-04-23 19:14   ` Jan Djärv
2007-04-23 22:12     ` Stephen Berman
2007-04-23 22:50       ` YAMAMOTO Mitsuharu
2007-04-24  1:10         ` YAMAMOTO Mitsuharu
2007-04-26 20:58           ` Stephen Berman
2007-04-27  8:57             ` YAMAMOTO Mitsuharu
2007-04-28  4:06               ` Richard Stallman
2007-04-29  7:35                 ` YAMAMOTO Mitsuharu
2007-04-29 21:41                   ` Richard Stallman
2007-05-01  8:30                     ` YAMAMOTO Mitsuharu
2007-05-02  0:12                       ` Richard Stallman
2007-04-29  7:51                 ` David Kastrup
2007-04-29  9:25                   ` Nick Roberts
2007-04-29 21:41                   ` Richard Stallman
2007-04-29 22:14                     ` David Kastrup [this message]
2007-05-01  0:23                       ` YAMAMOTO Mitsuharu
2007-04-24 14:08     ` Stefan Monnier
2007-04-24 14:49       ` Jan Djärv
2007-04-24 18:27       ` Glenn Morris
2007-04-25  8:47         ` Jan Djärv
2007-04-25 14:36           ` Stefan Monnier
2007-04-25 14:50             ` Jan Djärv
2007-04-25 18:30               ` Jan Djärv
2007-04-25 19:34                 ` Stefan Monnier
2007-04-25 19:44                 ` YAMAMOTO Mitsuharu
2007-04-26  5:58                   ` Jan Djärv
2007-04-26  8:35                     ` YAMAMOTO Mitsuharu
2007-04-26  3:08                 ` Glenn Morris
2007-04-26 20:59                 ` Stephen Berman
2007-04-27  5:58                   ` Jan Djärv
2009-03-16  1:37                 ` YAMAMOTO Mitsuharu
2009-03-16 12:16                   ` David Reitter
2009-03-16 15:18                     ` Chong Yidong
2009-03-17  2:43                       ` YAMAMOTO Mitsuharu
2009-03-17  3:59                         ` Chong Yidong
2009-03-17  4:13                           ` YAMAMOTO Mitsuharu
2009-03-17  9:06                             ` YAMAMOTO Mitsuharu
2009-03-17 15:13                               ` Chong Yidong
2009-03-18  8:56                                 ` YAMAMOTO Mitsuharu

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=85647ebzgr.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    --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).