Date: Mon, 12 Feb 2001 17:27:18 -0800 From: "David O'Brien" <TrimYourCc@NUXI.com> To: Peter Wemm <peter@netplex.com.au> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Patch for FILE problems (was Re: -CURRENT is bad for me...) Message-ID: <20010212172717.M3038@dragon.nuxi.com> In-Reply-To: <200102130120.f1D1KpU56194@mobile.wemm.org>; from peter@netplex.com.au on Mon, Feb 12, 2001 at 05:20:51PM -0800 References: <xzpd7cno08x.fsf@flood.ping.uio.no> <200102130120.f1D1KpU56194@mobile.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 12, 2001 at 05:20:51PM -0800, Peter Wemm wrote:
> It avoids the current problem:
> - RELENG_4 bumped from 3.0 to 4.0
> - this forced a premature 4.0->5.0 bump in -current
Actually "NO". I bumped libc.so because Garret said he had changes ready
for libc, but was waiting for someone to bump the shared version number.
> - we missed our chance for major changes. (!!!)
In the past, once it was bumped, incompatable changes to libc.so were
fair game for -CURRENT.
> If we had taken -current to 500, we could go to 501, 502, etc as
> required to stop killing our developers, and prior to entering 5.0-BETA we
> go back to the next sequentially available major number (be it 5, or 6
> if RELENG_4 bumps again).
/me wonders if we'll also do something about all the other things we do
that kills our developers in -current......
--
-- David (obrien@FreeBSD.org)
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010212172717.M3038>