Date: Wed, 28 Jun 2000 18:10:10 -0700 (PDT) From: Kris Kennaway <kris@FreeBSD.org> To: Doug Barton <Doug@gorean.org> Cc: "Andrey A. Chernov" <ache@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: backporting to 3.5 Message-ID: <Pine.BSF.4.21.0006281808150.42454-100000@freefall.freebsd.org> In-Reply-To: <Pine.BSF.4.21.0006281608580.43075-100000@dt052n3e.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 Jun 2000, Doug Barton wrote:
> Is there going to be a policy regarding what to backport to
> 3.5? My understanding was that once the 3.5-RELEASE tag was laid down all
> that would go back would be bug/security fixes. My personal opinion is
> that if we backport too much we reduce the users' motivation to move to
> 4.x, not to mention the maintenance problems as a discouragement to
> committers who do feature development.
We still sometimes merge back 2.2 and even 2.1 - it's really a matter of
whether the committer is motivated to do so (e.g. if they have machines
which need the change). What has dropped is the level of expectation that
committers should merge their applicable changes back (not that many
people follow this).
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0006281808150.42454-100000>