emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: when emacs 22.1 release will ready?


From: Leo
Subject: Re: when emacs 22.1 release will ready?
Date: Tue, 01 May 2007 00:26:42 +0100
User-agent: No Gnus v0.6, Emacs/23.0.0.18 (2007-04-29), Fedora 6.93 gnu/linux

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

> "Alex Ott" <address@hidden> 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)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]