From owner-freebsd-stable@FreeBSD.ORG Tue May 29 15:26:41 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C78216A46D for ; Tue, 29 May 2007 15:26:41 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mx1.freebsd.org (Postfix) with ESMTP id 35A1113C43E for ; Tue, 29 May 2007 15:26:41 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from bmah.local (hornet.kitchenlab.org [64.142.31.105]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id l4TFQZSm029305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 May 2007 08:26:35 -0700 Message-ID: <465C4624.5020004@freebsd.org> Date: Tue, 29 May 2007 08:26:28 -0700 From: "Bruce A. Mah" User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: LI Xin References: <465BF62B.6090904@vwsoft.com> <20070529102929.GA49322@owl.midgard.homeip.net> <465C06CE.6000703@delphij.net> In-Reply-To: <465C06CE.6000703@delphij.net> X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDEF999043FFC77325E15EB77" Cc: Volker , stable@freebsd.org Subject: Re: release cycle X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2007 15:26:41 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDEF999043FFC77325E15EB77 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, LI Xin wrote: > Hi, Erik, >=20 > Erik Trulsson wrote: >> On Tue, May 29, 2007 at 11:45:15AM +0200, Volker wrote: > [...] >>> I know there's a release cycle for 7-CURRENT planned next June but >>> IMHO it can be delayed for some weeks. >>> >>> What does the core and releng team think? It might do good. >> A quick release cycle for a release from -STABLE sounds like a bad ide= a. >> There have been enough new things that have gone into the 6-STABLE bra= nch >> that a full release cycle seems warranted. >=20 > I would say that just tagging -STABLE tree as "RELEASE" is a very bad > idea, however, it would not be too bad if we take RELENG_6_2 as a > codebase and add the following bugfixes: >=20 > - zonelim fixes (very helpful for heavy loaded systems). > - some socket locking fixes (settled for a long time). > - driver updates, like RAID driver bugfixes. >=20 > Therefore, from src/'s view, I think it would not be too bad to make a > point release that merges some (well tested) bugfixes in, or at least, > provide a patchset as an errata for 6.2-R. We've done point releases in the past but only in cases where there were severe problems and/or regressions with released versions. Look at the announcements and release notes for 4.6.2-RELEASE and 5.2.1-RELEASE...these were the two most recent instances where we did this. There's a reason for this...it's a lot of effort. Folks should realize that making a new release (even a new point release) is not just a matter of tagging the tree and typing "make release". We (re@) need to figure out exactly what bugs are to be fixed, get the changes merged and tested, build at least one release candidate, get that tested, and finally build a set of RELEASE bits and push them out. And that's just the src/ part. The original poster was mostly concerned about the X.org upgrade, which as we all know lives in the ports/ tree. If we were to do a "point release" we'd basically require a complete port freeze and package build run. I believe that we did do that for both 4.6.2-RELEASE and 5.2.1-RELEASE. As someone's pointed out, the ports committers are still fixing up some of the rough edges around the X.org update, so that part of the tree isn't even ready to go yet. The way I see it (and this is just my personal opinion, not an official statement from re@), doing a point release now would be a distraction from our next scheduled release, which is 7.0. Bruce. PS. This having been said I know there are some kernel fixes that were candidates for errata against 6.2-RELEASE...I'm not sure what their current state is. I'd like to see some of these get applied to RELENG_6_= 2. --------------enigDEF999043FFC77325E15EB77 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGXEYk2MoxcVugUsMRAj1JAJ9BA4wzPUkpPXCEmmAkiZkQ9M641gCfTAff CfryK9lNHYNO/jYltq0Z6yE= =RioI -----END PGP SIGNATURE----- --------------enigDEF999043FFC77325E15EB77--