Date: Thu, 14 Sep 1995 16:29:43 -0400 (EDT) From: Chuck Robey <chuckr@eng.umd.edu> To: "Ugen J.S.Antsilevich" <ugen@latte.worldbank.org> Cc: freebsd-current@freebsd.org Subject: Re: What is where... Message-ID: <Pine.SUN.3.91.950914162652.9344B-100000@espresso.eng.umd.edu> In-Reply-To: <Chameleon.4.00.4.950914095959.ugen@ugen>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 14 Sep 1995, Ugen J.S.Antsilevich wrote: > Hi guys..sorta lame question but forgive me, i was out of business for > so long: > > so i c the last released version was 2.0.5 > -stable = 2.1.0 > -current = 2.2.0 (???) > > So if i am going to write something and i want it into 2.1.0 release > i should put it into stable? OR there is not any development on stable? > If there is what's the policy of commits etc...? > If i put something in 2.2.0 (suppose for a minute, it works :^))) it is > going to be only there, right? Way I understand it, the idea is no new functionality in 2.1 (STABLE), just bug fixes. I think it's been violated, but only for stuff that's gone thru testing by sitting in 2.2 (CURRENT) for awhile, and even then, there's some argument. The idea is for the 2.1 release to approach the kind of reputation for reliability that our old, revered 1.1.5.1 release has. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+-----------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.950914162652.9344B-100000>