Date: Thu, 13 Sep 2007 09:01:46 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Aristedes Maniatis <ari@ish.com.au> Cc: freebsd-current@freebsd.org Subject: Re: 7 release timetable Message-ID: <20070913090146.ueiy855n2808w4ss@webmail.leidinger.net> In-Reply-To: <2E4631F6-0AE9-4451-A51A-BCF4DB8DECEC@ish.com.au> References: <2E4631F6-0AE9-4451-A51A-BCF4DB8DECEC@ish.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Aristedes Maniatis <ari@ish.com.au> (from Thu, 13 Sep 2007 =20 09:22:10 +1000): > I don't want this to sound like a "is it ready yet?" email, but as we > are rolling out some new servers in the next months I'd like to get > some idea of whether it is time for us to start testing hardware and > configurations against current, ready for deployment in the not distant > future. In particular I am very interested in the excellent > improvements for SMP and mysql performance. The source of 7-current is frozen. This means all changes have to be =20 approved by our release engineering team. If you test _now_ and report =20 problems you may see, the chance is high that those problems get fixed =20 before 7.0 is released. Some people already use 7-current in =20 production (but this is not recommended by the developers of FreeBSD). > * The bug reports at http://www.freebsd.org/cgi/query-pr-summary.cgi > don't seem to correlate with activity on current. Is there a separate > bug tracker so that users like myself can see what known bugs remain > prior to release? Other open source projects I am affiliated with (for > example those at Apache) use bug tracking databases in this way. Or is > FreeBSD a little more organic with each developer keeping their own > todo list. There's no separate bug tracker. Typically bugs for -current are =20 reported on this mailinglist and people either directly have a look at =20 it, or request that people open up a bug report in our bug tracker. =20 The critical bugs are currently tracked by the release engineering =20 team. There was even a commit to the webpages which contains an =20 initial list of known problems prior to beta1, but this list didn't =20 contain all bugs which where reported to current@. I don't know if the =20 list of known defects the release engineering team has is the same as =20 what is available in CVS. > * Is there a set release schedule and known bugs notes for snapshots? No, there's nothing like this for snapshots. This would be too much =20 work. We only have this for releases. > I'd like to try a snapshot but I don't know whether to wait a > day/week/month for the next one. Or are they released just when someone > thinks the source is in a good overall state? They are released periodically. AFAIK there's no runability check =20 before a snapshot goes out, the only requirement is that it builds =20 correctly. Bye, Alexander. --=20 The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. =09=09-- Justice Louis D. Brandeis http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070913090146.ueiy855n2808w4ss>