Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Mar 2009 10:51:45 +0100
From:      "Jack Raats" <jack@jarasoft.net>
To:        "Robert Watson" <rwatson@FreeBSD.org>
Cc:        kama <kama@pvp.se>, Ken Smith <kensmith@cse.Buffalo.EDU>, freebsd-stable <freebsd-stable@freebsd.org>
Subject:   Re: FreeBSD 7.2 Release process starting...
Message-ID:  <997A6168643B453CB90D2A25AD7AE563@jarasoft.net>
References:  <1237299551.80881.16.camel@bauer.cse.buffalo.edu><20090318102134.D55869@ns1.as.pvp.se> <alpine.BSF.2.00.0903181134380.99720@fledge.watson.org> <91210A8474CD444786833AFD3542BCCA@jarasoft.net> <alpine.BSF.2.00.0903190927320.99520@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
From: "Robert Watson" <rwatson@FreeBSD.org>

>> About FreeBSD 6.4. If you consider to make new 6.4 iso's, perhaps it 
>> would be better to think about an 6.5 release????
>
> It's a question of bandwidth for the release engineering team, ports team, 
> security officer team, etc -- I think a 6.5 is pretty much out of the 
> question right now with 8.0 preparing to ramp up and 7.2 now in flight. 
> That gives us a short menu of options:
>
> - Errata patches
> - Errata patches + ISO reroll
> - Point release
>
> Because of the boot loader issues, errata patches don't really cut it 
> alone, as if you can't install, you definitely can't apply errata patches 
> :-).  This suggests a reroll or a point release.

This reminds me of FreeBSD 4.6 and FreeBSD 4.6.2 (The first FreeBSD I ever 
used was 4.6, that's why I remember)

> For me the distinction remains fuzzy, but I think a key to either approach 
> would be avoiding having to fully re-QA, do BETAs, build new packages, 
> etc. This suggests taking RELENG_6_4 on some date, perhaps rebranching if 
> it's a point release, or not if it's an ISO reroll, and bundling it with 
> exactly the same packages we shipped in 6.4 (etc) and bumping a few 
> documentation parts.

Indeed, that's a lot of work for an errata patch.

Jack




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