Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newsroom.utas.edu.au!munnari.OZ.AU!news.hawaii.edu!ames!hookup!gatech2!news.sprintlink.net!newsfeed.internetmci.com!in1.uu.net!spcuna!tzlink.j51.com!lepslog From: lepslog@j51.com (Louis Epstein) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD newbie questions.... Date: 12 Nov 1995 23:48:53 GMT Organization: TZ-Link, a public-access online community in Nyack, NY. Lines: 22 Message-ID: <486155$3kf@tzlink.j51.com> References: <1995Nov9.041305.16191@oasis.enmu.edu> <30A23B47.446B9B3D@FreeBSD.org> <483unk$po@tzlink.j51.com> <30A6419E.1C4EBE01@FreeBSD.org> NNTP-Posting-Host: j51.com X-Newsreader: TIN [version 1.2 PL2] Jordan K. Hubbard (jkh@FreeBSD.org) wrote: : Here's basically how it works: : We have two branches of FreeBSD currently, -stable and -current. : To further confuse things a little, the -stable branch was formed at : 2.0.5 and so everything subsequent to that has basically been considered : "2.1-in-waiting." The SNAPs are always previews of whatever release is : coming up, so every SNAP you've seen has been somewhere along the : timeline of 2.0.5 -> 2.1. After 2.1 is released, -stable will continue : but marching now towards 2.1.1 and beyond. Any SNAPs I release along : that branch will therefor be called 2.1.1-MMDDYY-SNAP. : Now, since it would be a pretty serious cramping of development to : constrain everyone to a code base that wasn't changing except in very : small increments, we have another branch called -current, which is : literally the day-to-day bleeding edge development effort leading to the : next big jump: FreeBSD 2.2. FreeBSD 3.x,I take it,will be the 64-bit implementations of circa 1998? Will another "return to the well" of Berkeley be required for the 32->64 bit jump??