From owner-freebsd-current  Sat Sep 16 12:38:31 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA03148
          for current-outgoing; Sat, 16 Sep 1995 12:38:31 -0700
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA03137
          ; Sat, 16 Sep 1995 12:38:28 -0700
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA01662; Sat, 16 Sep 1995 12:38:21 -0700
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199509161938.MAA01662@GndRsh.aac.dev.com>
Subject: Re: Which SUP files are available and where ?
To: paul@FreeBSD.org
Date: Sat, 16 Sep 1995 12:38:20 -0700 (PDT)
Cc: pete@sms.fi, davidg@Root.COM, current@FreeBSD.org
In-Reply-To: <199509161549.QAA02952@server.netcraft.co.uk> from "Paul Richards" at Sep 16, 95 04:49:58 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1640      
Sender: owner-current@FreeBSD.org
Precedence: bulk

> 
> In reply to Petri Helenius who said
> > 
> > David Greenman writes:
> >  > >
> >  > >  Ok, if this is the general consensus, when will 2.1 be available?
> >  > 
> >  >    "Soon". It's looking very good indeed.
> >  > 
> >  > -DG
> > 
> > Will there be 2.2-STABLE and 2.3-CURRENT after the 2.1-RELEASE happens?
> > I'm for this because I see it very valuable to have two branches of code
> > in addition to releases. -STABLE has proven it's right to exist, IMO.
> > 
> 
> Me too. I know it's more work for David (or someone anyway) but it allows
> bug smashing to be done over a longer period and also, I'm running some
> critical machines now and the sig 11 problem would have floored me but I'm
> happy to run -stable branches and put up with occasional glitches. It means
> we can run the next potential release in real environemnts for longer
> periods than we have in the past.

Not only that, part of the intent of doing the release work on branches
means FreeBSD now has a place to commit critical but fixes (after the 
``RELENG_2_1_0_RELEASE'' tag, and can produce small ``critical fix''
upgrade kits for the 2.1.0 release (actually create a 2.1.1) easily
and without impacting developement or 2.2 work.

If the tags are maintained as I had been doing them it should also
be quite easy to produce 2.0.5 vs 2.1.0 diffs (though they are going
to be _HUGE_.)  And even things like 2.1.0 vs -current diffs (which
due to Davids Massive work is actuall not that bad of a diff).


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD