(dropping Cc to pkg-xfce-devel@) On 18/04/07 at 17:02 +0200, Frans Pop wrote: > On Wednesday 18 April 2007 16:38, Simon Huggins wrote: > > There are always things that miss a release but had the freeze been > > pushed back to February say (two months before the release as per the > > original Oct -> Dec intention) then the January release of 4.4.0 may > > well have been deemed stable enough to ship. Who knows. > > OTOH, if the freeze had been pushed back, there would undoubtedly have > been new uploads or packages accepted into testing that would have had > serious issues and would have caused additional delays. > > From what I have seen during both the Sarge and Etch releases, a lot of > developers simply don't care about stabilization and upgrade paths, or at > least not enough to do some dedicated testing. I ran several rebuilds of the archive starting mid-october 2006, and until the freeze, the number of failures didn't really decreased, despite the systematic RC bug filing (I don't have the data to back that anymore, unfortunately). Many bugs were fixed, but new uploads introduced many new ones. I really like the idea of the "Upstream Version Freeze" that Ubuntu uses. During the next release cycle, it would be great to experiment that by enforcing an UVF of one or two weeks before the full freeze. This would give some time to maintainers to make sure that everything is OK with their packages, without putting too much load on the release team (only new upstream versions would have to be unblocked by the RT). Looking at the workflow of the release team during the etch cycle, I have also been thinking about the use of a simple ticket system for unblock requests. Have you considered this ? It would allow to sort requests according to relevant fields, like time of arrival, number of popcon installs, etc. Also, it could do some pre-processing, like running debdiff, making it easier to answer simple requests. if this is considered useful, this could be a nice project for SoC 2008... Cheers, -- | Lucas Nussbaum | lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F |
Attachment:
signature.asc
Description: Digital signature