Return to BSD News archive
#! rnews 1910 bsd Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!chi-news.cic.net!newsfeed.internetmci.com!in2.uu.net!tcsi.tcs.com!agate!reason.cdrom.com!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD newbie questions.... Date: Sun, 12 Nov 1995 10:49:02 -0800 Organization: Walnut Creek CDROM Lines: 24 Message-ID: <30A6419E.1C4EBE01@FreeBSD.org> References: <1995Nov9.041305.16191@oasis.enmu.edu> <30A23B47.446B9B3D@FreeBSD.org> <483unk$po@tzlink.j51.com> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b2 (X11; I; FreeBSD 2.1-STABLE i386) To: Louis Epstein <lepslog@j51.com> 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. -current has a lot of stuff not found in -stable like early IPX support, NFS v3, PCCARD hot insert/removal code and other rather sweeping changes aimed improving the system in larger ways than we'd risk in -stable. Both are available via sup or ftp. -- Jordan