Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!info.ucla.edu!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: next release, when? Date: 7 Jan 1996 23:19:45 GMT Organization: University of California, Berkeley Lines: 26 Message-ID: <4cpkei$k74@agate.berkeley.edu> References: <4ck9pd$j3n@news.csus.edu> <4cl4r9$p17@agate.berkeley.edu> <HAFNER.96Jan7141622@dartpub.augusta.de> NNTP-Posting-Host: violet.berkeley.edu In article <HAFNER.96Jan7141622@dartpub.augusta.de>, Walter 'madhouse' Hafner <hafner@dartpub.augusta.de> wrote: >JKH> Hard to say, but there's general plan to try and release 2.2 around >JKH> the end of this summer. > >End of summer ... hmmm ... remember the schedule for 2.1? ;-) Now you know why I hate it when people ask that question - I'm forced to make unrealistic predictions! :-) Seriously, the situation we have today is a little different than the one we had immediately following 2.0, when we tried to make our 2.1 time-table. We were still trying to merge everything directly from -current, and this turned into a tracking nightmare of such magnitude that we released 2.0.5 as an interim release to try and break the problem into two smaller pieces. Starting with 2.0.5, we finally wised-up and went to a two-track release system. 2.1 following 2.0.5 was *significantly* easier, and I expect 2.1.1 (or whatever point-release number we give it) will be easier still. It will be released sometime this spring. All this also allows us to be working on 2.2 *now*, as we have since June 1995, so by the time next June rolls around we'll have been hacking 2.2 for a solid year. If we can't get a release together in a year, we should all give up and go into beet farming anyway.. :-) Jordan