OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: Stable branch
From: Brett Glass (brettlariat.org)
Date: Thu Oct 05 2000 - 12:03:42 CDT

At 04:06 AM 10/5/2000, Ralph Huntington wrote:

>Stable branch is very important for production use and should incorporate
>bug fixes and security patches, but not feature enhancements. The extent
>of support and maintenance for stable should be one major release prior to
>the latest release (not current), i.e., since 4.x-RELEASE is the latest,
>then 3.x-STABLE hould be supported with bug fixes and security patches
>until a 5.x-RELEASE is out.
>
>Does this seem unreasonable? -=r=-

Perhaps this should be formalized as three branches:

Branch name: Bug/security New features? "Breakable" for
                       fixes? a day or more?

-PRODUCTION YES NO NO

-STABLE YES YES, PREFERABLY NO
                                        AFTER TESTING
                                        IN -CURRENT

-DEVELOPMENT YES YES YES
(formerly -CURRENT)

What do you think of this as a model for what people seem to be
asking for?

--Brett

To Unsubscribe: send mail to majordomoFreeBSD.org
with "unsubscribe freebsd-security" in the body of the message