On Mon, 7 Apr 2008 13:24:46 -0400 Jerry McAllister <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 07, 2008 at 01:11:59PM -0400, Tsu-Fan Cheng wrote: > > On Mon, Apr 7, 2008 at 1:08 PM, Matthew Seaman > > <[EMAIL PROTECTED]> wrote: > > > Tsu-Fan Cheng wrote: > > > > sorry, I just read some articles in the mailing list, it's > > > > RELENG_7 for stable, 7_0 is for current. > > > Nope. > > > RELENG_7_0 is for 7.0-RELEASE > > > RELENG_7 is for 7.0-STABLE (at the moment) > > > . is for 8-CURRENT > > so in a sense, 7.0-release is for developers, and 7.0-stable for end > > users, right? > No. 7.0-release is the final snapshot of 7.0. Current is > for developers and stable is a more cleaned up version of current. > Current is the bleeding edge. > Stable is sort of like a beta > and release is the final, cleaned up and built and tested release. > > The confusing thing is there can be more than one branch being > worked on. At the moment there is 7.xxx and 8.xxx. There can > be stable and release for each. The head is where current is > made which is 8.xxx now. > If something is built in to current that is wanted more immediately, > it gets merged in to the less bleeding edge tracks. The process for > that is called 'Merge From Current' usually called MFC - as in 'that > feature (or fix) was MFCed this morning'. It is amazing how often this question arises. I guess the manual does not explain the different 'tags' and branches thoroughly enough. -- Gerard [EMAIL PROTECTED] "The Schizophrenic: An Unauthorized Autobiography"
Description: PGP signature