Date: Fri, 16 Aug 1996 15:59:06 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: rkw@dataplex.net (Richard Wackerbarth) Cc: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>, stable@freebsd.org Subject: Re: Sup-ing stable Message-ID: <199608162159.PAA08561@rocky.mt.sri.com> In-Reply-To: <v02140b02ae3a8b430003@[199.183.109.242]> References: <v02140b02ae3a8b430003@[199.183.109.242]>
next in thread | previous in thread | raw e-mail | index | archive | help
> >I think there is enough confusion out there that the strings should be > >changed to this: > >TYPE="FreeBSD" > >REVISION="2.1.5" > >BRANCH="STABLE" > > Well, that is your opinion. My opinion is slightly different. > Here is my interpretation of the way things should be... > > "Stable", and for that matter "current", do not really designate > development branches. But, they *do* designate development branches. >I feel that they are simply aliases that reflect the > state of development. Using both "2.1.5" and "STABLE" is redundant. If so, then why do we have '2.1-STABLE'? You just said that 2.1.5 and STABLE are the same. > I think that "2.1" is the proper name of the branch. It is the name of the branch, but the confusion lies in the users, not the developers. Recent usage has been that 2.1-STABLE is 2.1 + stable patches. Keeping the -stable branch named to '2.1-STABLE' is true, although somewhat misleading since it really is 2.1.5 + stable patches'. In any case, I changed the strings to avoid the confusion which I felt occurred and agree with, or else we wouldn't be having this discussion. > However, to help avoid confusion among the uninitiated, perhaps we should > call today's version "FreeBSD 2.1.5-154","FreeBSD 2.1.5p154", or something > similar. This implies the users use CTM, which is definitely not the case for many users. CTM is only one of the 4 (5?) different distribution methods used. 1) CD-ROM (I'll lump all users of 'Releases' in the same manner). There is very little room for confusion here, except when a release is re-rolled using the same name. :) 2) Remote CVS - The release is designated by the date of the most recent update, so one can return to it using a particular date if necessary (although this doesn't work on branches). The state of the system is determined by the particular revisions on the files. 3) CTM - Richard' favorite, which uses numbers to designate a particular revision. 4) SUP - No way of getting back to where you were before or knowing where you are except by knowing what data you last did a sup, but generally this isn't a big deal. 5) CVSup - This is a combination of Remove CVS and SUP, with the ability to checkout via date (on branches even), or if you get the actual CVS tree you can determine where you are via dates as well. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608162159.PAA08561>