From owner-freebsd-stable@FreeBSD.ORG  Sat Sep 20 04:41:49 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8C1B51065671
	for <freebsd-stable@FreeBSD.org>; Sat, 20 Sep 2008 04:41:49 +0000 (UTC)
	(envelope-from gpalmer@freebsd.org)
Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1])
	by mx1.freebsd.org (Postfix) with ESMTP id 5E17C8FC0A
	for <freebsd-stable@FreeBSD.org>; Sat, 20 Sep 2008 04:41:49 +0000 (UTC)
	(envelope-from gpalmer@freebsd.org)
Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD))
	id 1KguI0-0000Be-EN; Sat, 20 Sep 2008 00:41:48 -0400
Date: Sat, 20 Sep 2008 00:41:48 -0400
From: Gary Palmer <gpalmer@freebsd.org>
To: Jo Rhett <jrhett@netconsonance.com>
Message-ID: <20080920044148.GA60230@in-addr.com>
References: <alpine.BSF.1.10.0809180022580.13100@fledge.watson.org>
	<658B8861-1E78-4767-8D3D-8B79CC0BD45F@netconsonance.com>
	<alpine.BSF.1.10.0809181935540.16464@fledge.watson.org>
	<15F15FD1-3C53-4018-8792-BC63289DC4C2@netconsonance.com>
	<448wtpcikb.fsf@be-well.ilk.org>
	<C096D142-4572-48DF-8CCA-053B41003A07@netconsonance.com>
	<alpine.BSF.1.10.0809191158330.40909@fledge.watson.org>
	<34C3D54B-C88C-4C36-B1FE-C07FC27F8CB5@netconsonance.com>
	<20080920020703.GA82392@phat.za.net>
	<851F09A2-788D-4343-9E00-A0AB5C3AC063@netconsonance.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <851F09A2-788D-4343-9E00-A0AB5C3AC063@netconsonance.com>
Cc: freebsd-stable <freebsd-stable@FreeBSD.org>
Subject: Re: Upcoming Releases Schedule...
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Sep 2008 04:41:49 -0000

On Fri, Sep 19, 2008 at 07:38:32PM -0700, Jo Rhett wrote:
>  Without input from the current release team extending the support  
> schedule is not possible.

Inquiry - is release team the constraint?

Or to put it another way, what to you is "support" in terms of
FreeBSD releases?

As far as I am aware, if you stick on a RELENG_X_Y_Z_RELEASE tag 
then the most you get is security fixes.  No new features,
no new drivers, no bugfixes.  So if I am interpreting things
correctly, you are asking for security fixes to be ported to
RELEASE tagged branches for longer?

So is release team the contrained resource in your problem?
I am not denying that *any* part of the FreeBSD team is not
resource constrained, but I'm wondering if you're examining
the correct area. 

Note: I am not up on the internals of modern FreeBSD
release engineering and maintenance nor the relationship
between "staff" functions, so I may be barking up the wrong
telephone pole.

Regards,

Gary