From: Rob Landley <rob@landley.net>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Deja vu...
Date: Sun, 12 Oct 2003 23:53:58 -0500 [thread overview]
Message-ID: <200310122353.58935.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0310081235280.4017-100000@home.osdl.org>
Correct me if I'm wrong, but I vaguely remember back at the end of 1998 the
big "let's ship 2.2" push crescendoed towards the end of the year after two
and a half years of development, there was the big push to ship it by
christmas, then by new years, and after missing both deadlines it shipped a
dot-zero release in january 1999, followed shortly thereafter by a "brown
paper bag" bugfix release.
The big "let's ship 2.4" push crescendoed towards the end of 2000, after
about two and a half years of development (give or take the 2.2 stabilization
period before 2.3 forked off), there was a big push to ship it by christmas,
then by new years, and after missing both deadlines it shipped a dot-zero at
the start of january 2001, followed by the brown paper bag...
It's now coming up on two and a half years of development towards 2.6. It's
getting towards the end of the year. (I take Linus is aiming to have the 2.6
release out by this christmas? ;)
Does this seem kind of familiar to anyone else...?
Rob
(I don't remember if 2.1 had a new feature freeze a year or so before the
final code freeze the way 2.3 and 2.5 did, but it does seem we've got a
pattern going here. But then I'm sleep-deprived right now, and could easily
be imagining it...)
next prev parent reply other threads:[~2003-10-13 6:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 19:47 Linux 2.6.0-test7 - stability freeze Linus Torvalds
2003-10-08 23:57 ` Linux 2.6.0-test7 - stability freeze (compile stats) John Cherry
2003-10-09 12:45 ` Linux 2.6.0-test7 - compile/boot success iain d broadfoot
2003-10-09 13:29 ` 2.6.0-test7 BLK_DEV_FD dependence on ISA breakage Mikael Pettersson
2003-10-09 14:05 ` Andrew Morton
2003-10-09 18:04 ` Anton Blanchard
2003-10-09 18:18 ` Arun Sharma
2003-10-09 20:21 ` Mikael Pettersson
2003-10-10 11:55 ` Geert Uytterhoeven
2003-10-13 4:52 ` Linux 2.6.0-test7 - stability freeze Rob Landley
2003-10-13 4:53 ` Rob Landley [this message]
2003-10-13 17:34 ` Olaf Hering
2003-10-13 20:50 ` gcc -msoft-float [Was: Linux 2.6.0-test7 - stability freeze] Sam Ravnborg
2003-10-14 8:12 ` Olaf Hering
2003-10-14 8:31 ` Arjan van de Ven
2003-10-14 8:50 ` Olaf Hering
2003-10-14 11:40 ` Linux 2.6.0-test7 - stability freeze Jakub Jelinek
2003-10-15 17:27 ` Linux 2.6.0-test7 - Suspend to Disk success Jonathan McDowell
2003-10-15 21:00 ` Daniele Venzano
2003-10-16 14:06 ` Pavel Machek
2003-10-18 17:35 ` Daniele Venzano
2003-10-18 17:54 ` Daniele Venzano
2003-10-18 18:01 ` Pavel Machek
2003-10-18 20:48 ` Daniele Venzano
2003-10-19 7:38 ` Daniele Venzano
2003-10-20 19:08 ` Patrick Mochel
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=200310122353.58935.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox