Messages in this thread | | | Date | Fri, 7 Jan 2000 19:23:14 +0100 (MET) | From | Marco Colombo <> | Subject | Re: Standard Development Integration |
| |
On Tue, 4 Jan 2000, Alan Cox wrote:
> Date: Tue, 4 Jan 2000 19:19:34 +0000 (GMT) > From: Alan Cox <alan@lxorguk.ukuu.org.uk> > To: Sam Powell <sam.powell@cwcom.net> > Cc: linux-kernel@vger.rutgers.edu > Subject: Re: Standard Development Integration > > > How does the versioning work. Doy uo just plop features into > > 2.3.x, and when they all work, put it into a new 2.2.x? Also,=20 > > when do you decide the kernel has developed sufficiently to > > deserve a new major/minor number revision? > > We drop features into 2.3.x until its roughly where we want it. Linus then > starts getting very hard to get new features past and the stuff is stabilised > then it pops out probably as 2.4 and we start 2.5 a while later.
I've always wondered, why start 2.5 later? Just spawn the 2.5 branch when 2.4.0-pre appears. So development needs not to stop. I think that there's so much pressure on putting features inside 2.3 now (wasn't it feature-freezed?) because 2.6 is SO far away that many can't just wait for it.
Moreover, when 2.4 is out, there will be no development branch. So people will start developing against it (but wait, shouldn't be a *stable* release?). It already happened (RAID, ReiserFS?) and will probably happen with ext3.
Having a 2.5 branch soon also means a 2.6 is coming sooner, and maybe we can have ext3 in it.
> > (PS When is ext3 to be introduced?) > > As standard, post 2.4, usably - already.
That's it. "post 2.4" means adding it to a "stable" beast. Just put it in 2.5 (very soon) and release it in 2.6 (or backport it to 2.4 in case of huge demand). Right now we have NEW features which need to be ported from the (stable) 2.2 branch to the (feature-freezed) 2.3 branch. Weird at least, don't you think so?.
.TM.
-- ____/ ____/ / / / / Marco Colombo ___/ ___ / / Technical Manager / / / ESI s.r.l. _____/ _____/ _/ Colombo@ESI.it
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |