Date: Sun, 24 Feb 2008 10:34:54 -0800 From: "Bruce A. Mah" <bmah@freebsd.org> To: Will Froning <will.froning@gmail.com> Cc: Garrett Cooper <yanefbsd@gmail.com>, current@freebsd.org Subject: Re: Gathering a list of showstoppers for RELENG_7 Message-ID: <47C1B8CE.9060507@freebsd.org> In-Reply-To: <dea50a6c0802240829i44325f4bx9356e3a411dc8b67@mail.gmail.com> References: <511FC3E9-937C-475C-8F1B-39BA5347DBE0@gmail.com> <47C192C4.4080109@freebsd.org> <dea50a6c0802240829i44325f4bx9356e3a411dc8b67@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig526BC3BACB475ADBF7DB842B Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable If memory serves me right, Will Froning wrote: > Hello All, >=20 > On Sun, Feb 24, 2008 at 7:52 PM, Bruce A. Mah <bmah@freebsd.org> wrote:= >> If memory serves me right, Garrett Cooper wrote: >> >> > As part of the new Cisco FreeBSD ramp-up, I've noted that the= re's >> > been some concern about showstoppers for RELENG_7 as of late. So, I= >> > was just wondering what the current showstoppers are for 7.x and >> > possibly how I can help triage issues in the next couple weeks, etc= , >> > to accelerate the release a bit. >> > I may not have access to a PC at all times nor a FreeBSD mach= ine, but >> > I should be able to assign bugs or CC owners, or help debug some mo= re >> > common items. I'll also try getting VMware fusion in the upcoming w= eek >> > to work from my laptop and help out in some way shape or form in pe= rson. >> >> The release builds for 7.0 are underway now. >> >> What oftentimes happens very late in the release cycle (and this was >> true for 7.0) is that we find some issues that crop up that need to b= e >> fixed. They're usually assigned pretty quickly to "owners" (in fact = the >> owners are oftentimes the ones that report these problems), so many >> times there isn't a lot for other people to do, and these issues don'= t >> even make it into the PR database. >> >> I admit that we could (and should) do better in communicating status = to >> other developers and the community at large. This is mostly helpful = in >> the early and middle stages of the release cycle. >> >> This is clearly *not* to say that FreeBSD doesn't need help with >> testing, bug management, and so forth, in fact quite the opposite is >> true. I mean only to say that 7.0 doesn't have anything blocking it.= >=20 > Does that mean <http://www.freebsd.org/releases/7.0R/todo.html>; is outd= ated? The libkse item was fixed in early February, but we didn't note it here. = I just updated it...thanks for pointing that out! > /me is sooooo looking forward to a killer release! /me too! There *are* some outstanding issues in 7.0, for which we're=20 contemplating some errata notices (and hence patches for RELENG_7_0).=20 I'm being deliberately vague here because I don't want to commit us to=20 anything yet, but two *possible* items are some if_re fixes and a change = in TCP options handling. For errata items, we need to wait for the=20 actual release to wrap up (duh) and also give the fixes some "soak time" = in HEAD and RELENG_7. Cheers, Bruce. --------------enig526BC3BACB475ADBF7DB842B 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 iD8DBQFHwbjS2MoxcVugUsMRAn/5AJ9bRstJzLljJ0uRiWOXlyz0qIMVswCgtrOb g00HulEk+K4bDjZimZg/tOw= =ydzi -----END PGP SIGNATURE----- --------------enig526BC3BACB475ADBF7DB842B--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47C1B8CE.9060507>