From owner-freebsd-stable Thu Jun 6 02:05:02 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA12266 for stable-outgoing; Thu, 6 Jun 1996 02:05:02 -0700 (PDT) Received: from uu.elvisti.kiev.ua (acc0.elvisti.kiev.ua [193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA12244 for ; Thu, 6 Jun 1996 02:04:30 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id MAA11939; Thu, 6 Jun 1996 12:09:05 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id MAA08808; Thu, 6 Jun 1996 12:09:04 +0300 From: "Andrew V. Stesin" Message-Id: <199606060909.MAA08808@office.elvisti.kiev.ua> Subject: Re: Status of -stable To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 6 Jun 1996 12:09:04 +0300 (EET DST) Cc: stable@freebsd.org In-Reply-To: <29476.834043606@time.cdrom.com> from "Jordan K. Hubbard" at Jun 5, 96 11:46:46 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk # Since we can't use CVS to maintain long-term branches, we have to # stop doing that. With the next release of 2.1-stable (which will be # numbered "2.1.5") the 2.1-stable branch will be dead. Hurraaayyy!!! :-) # We will not # resurrect another -stable branch in its place, as previously planned, # and all development will take place in -current as it did before. We # may do short term branch development leading up to each new release, # but nothing like the 15 month run of the 2.1-stable branch! This has # simply been a nightmare and -stable has, at most, one or two more # months to live. # # In the short-to-medium term we'll probably go back to our old model of # freezing 2.2 periodically and trying to get it released. Or will it be a short-term "release" branch in CVS? -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1.