unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo <sdl.web@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: when emacs 22.1 release will ready?
Date: Tue, 01 May 2007 00:26:42 +0100	[thread overview]
Message-ID: <m2tzuxsatp.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: m38xcarzep.fsf@kfs-l.imdomain.dk

----- Kim F. Storm (2007-04-30) wrote:-----

> "Alex Ott" <alexott@gmail.com> writes:
>
>> Is any time boundaries for releasing of emacs 22.1?
>
> No.
>
>> Will some
>> pre-release message released some time before release 
>
> Indeed, there have been many "real soon now" pre-release messages at
> regular intervals for the last +3 years.
>
>
> Compare this to Linus' announcement for the just released 2.6.21 kernel:
>
> + So it's been over two and a half months, and while it's certainly not the
> + longest release cycle ever, it still dragged out a bit longer than I'd
> + have hoped for and it should have. As usual, I'd like to thank Adrian (and
> + the people who jumped on the entries Adrian had) for keeping everybody on
> + their toes with the regression list - there's a few entries there still,
> + but it got to the point where we didn't even know if they were real
> + regressions, and delaying things further just wasn't going to help.
>
> With a similar release procedure for Emacs, Emacs 22.1 had been
> released in 2004, and 23.4 would be ready for release next month.

Linus knows well:

"""
Linus Torvalds disagreed with Adrian's view that increasing the length
of the release cycle would improve stability, "regressions _increase_
with longer release cycles. They don't get fewer." He went on to add,
"you are ignoring the reality of development. The reality is that you
have to balance things. If you have a four-month release cycle, where
three and a half months are just 'wait for reports to trickle in from
testers', you simply won't get _anything_ done. People will throw their
hands up in frustration and go somewhere else." He continued: ......
"""

-- 
Leo <sdl.web AT gmail.com>                         (GPG Key: 9283AA3F)

  parent reply	other threads:[~2007-04-30 23:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-29 20:37 when emacs 22.1 release will ready? Alex Ott
2007-04-30  9:21 ` Kim F. Storm
2007-04-30  9:33   ` Lennart Borgman (gmail)
2007-04-30  9:38     ` Jason Rumney
2007-04-30  9:53       ` Lennart Borgman (gmail)
2007-04-30 19:10         ` Eli Zaretskii
2007-04-30 21:30           ` Lennart Borgman (gmail)
2007-04-30 23:29             ` Juanma Barranquero
2007-04-30  9:56     ` Thomas Hühn
2007-04-30 10:18       ` Lennart Borgman (gmail)
2007-04-30 10:15     ` joakim
2007-04-30 10:25       ` Lennart Borgman (gmail)
2007-04-30 22:10         ` Richard Stallman
2007-04-30 15:18       ` unit testing [was Re: when emacs 22.1 release will ready?] Stephen J. Turnbull
2007-04-30 10:09   ` when emacs 22.1 release will ready? Leo
2007-04-30 10:23     ` Lennart Borgman (gmail)
2007-04-30 10:37       ` Leo
2007-04-30 11:29         ` Thien-Thi Nguyen
2007-04-30 15:20     ` Chong Yidong
2007-04-30 23:26   ` Leo [this message]
2007-04-30 22:09 ` Richard Stallman

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=m2tzuxsatp.fsf@sl392.st-edmunds.cam.ac.uk \
    --to=sdl.web@gmail.com \
    --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 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).