From owner-freebsd-stable Tue Mar 28 7:49:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 1BB4837BD5C for ; Tue, 28 Mar 2000 07:49:35 -0800 (PST) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12ZyEx-000AqH-00; Tue, 28 Mar 2000 17:49:11 +0200 From: Sheldon Hearn To: Martin Cracauer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Let 3.x die ASAP? In-reply-to: Your message of "Tue, 28 Mar 2000 11:36:34 +0200." <20000328113633.A28085@cons.org> Date: Tue, 28 Mar 2000 17:49:11 +0200 Message-ID: <41680.954258551@axl.ops.uunet.co.za> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Mar 2000 11:36:34 +0200, Martin Cracauer wrote: > I am so impressed with the results of upgrading my more important > machines to 4.0 or 4-stable that I could imagine not to produce any > more 3.x releases. I must admit, during the 3.4-RELEASE code slush, I somehow got the impression that 3.4-RELEASE would be the last release on the RELENG_3 branch. I was happy with that and I hope it remains true. The only reasonable argument that I can think of for a 3.5-RELEASE is to have a kind of "closure" release for people who _must_ stick with the RELENG_3 branch because they've been advised to by project staff. Lots of people are in this position; I've read "then stick with RELENG_3" in response to quite a range of "but I have old hardware" complaints. The "closure" release that I envision is one in which there aren't any more serious bugs that can be fixed without merging back significant portions of the RELENG_4 branch. It would basically be the RELENG_3 branch "polished off". :-) Having said that, I don't like the idea one little bit, for exactly the reasons you listed in your original message. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message