Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Jun 2002 17:41:11 +0200
From:      Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To:        freebsd-stable@FreeBSD.ORG
Subject:   Re: 4.6-RELEASE delayed
Message-ID:  <20020601154111.GB7019@merlin.emma.line.org>
In-Reply-To: <200206011443.g51EhRb1027658@intruder.bmah.org>
References:  <200205311652.g4VGq5YV004136@intruder.bmah.org> <m3d6vc3vqg.fsf@merlin.emma.line.org> <200205312119.g4VLJm7d008902@intruder.bmah.org> <20020601113321.GC15739@merlin.emma.line.org> <200206011443.g51EhRb1027658@intruder.bmah.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 01 Jun 2002, Bruce A. Mah wrote:

> > Yup. I'm just wondering if a bugfix would be committed to 4.6-STABLE
> > (that usually should only receive security fixes).
> 
> I think you may be a little confused here.
> 
> The 4-STABLE development branch (with the CVS tag RELENG_4) will take on
> various names during its lifetime, including 4.6-STABLE, 4.7-PRERELEASE,
> and 4.7-RC.  It will eventually be the basis of 4.7.  It will definitely
> get the bugfix, once one is created.

Please apologize for not naming it 4.6-RELEASE (which is what I meant,
but did not write).

> The 4.6 release/security branch (with the CVS tag RELENG_4_6) will have
> version numbers of the form 4.6-RELEASE, 4.6-RELEASE-p1, 4.6-RELEASE-p2,
> and so forth.  It normally only gets security fixes and critical system
> bugfixes.  I think it's *way* too early to be thinking about applying an
> ATA tagged queueing bugfix to this branch, since the bugfix in question
> doesn't even exist yet.  (Neither does the branch, for that matter.)

Indeed, "security fixes and critical system bugfixes" is the key word I
was asking for. So it's possible, if the bugfix is isolated and directed
enough that it might get in. Let's hope for the best for the ATA stuff.

-- 
Matthias Andree

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020601154111.GB7019>