Date: Tue, 29 May 2007 10:00:52 -0700 From: "Bruce A. Mah" <bmah@freebsd.org> To: Colin Percival <cperciva@freebsd.org> Cc: stable@freebsd.org Subject: Re: release cycle Message-ID: <465C5C44.8060701@freebsd.org> In-Reply-To: <465C49B5.8080003@freebsd.org> References: <465BF62B.6090904@vwsoft.com> <20070529102929.GA49322@owl.midgard.homeip.net> <465C06CE.6000703@delphij.net> <465C4624.5020004@freebsd.org> <465C49B5.8080003@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9A71B398435148D55065F2EE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Colin Percival wrote: > Bruce A. Mah wrote: >> We've done point releases in the past but only in cases where there we= re >> severe problems and/or regressions with released versions. Look at th= e >> 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 an= d >> push them out. >=20 > I point releases have been obsoleted by errata notices. In the past wh= en > X.Y.Z-RELEASE has happened, it has been because of critical bugs in the= > X.Y-RELEASE which there wasn't any other mechanism to fix. Now that we= > have errata noticed and FreeBSD Update is in the base system, it's vast= ly > easier for users to run "freebsd-update fetch install" than it is for t= hem > to upgrade to a new release. That's a good point. I'd be happy if we never had to do another point release again, since we have to do probably half the work of a normal release cycle but it's completely unexpected and unscheduled. BTW I finally added some mention of freebsd-update(8) to the section of the release notes that talks about upgrading FreeBSD. Only on HEAD for now, I'll put this on RELENG_6 when I get a Round Tuit. >> PS. This having been said I know there are some kernel fixes that wer= e >> candidates for errata against 6.2-RELEASE...I'm not sure what their >> current state is. >=20 > Don't ask me, I just approve the errata which you send to me. Which ha= sn't > been anything at all lately. :-) Ah no, we haven't sent you anything as of late, and that's the problem. = :-) Bruce. --------------enig9A71B398435148D55065F2EE 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 iD8DBQFGXFxE2MoxcVugUsMRAgsQAKCOYe4SYFY0Hj7nhctMJ3tAph49dQCffwhY OI4mTUGDQJsDXBRq9Llb29M= =hu+8 -----END PGP SIGNATURE----- --------------enig9A71B398435148D55065F2EE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465C5C44.8060701>