FREEZE RESCHEDULED
I was too hasty when declaring this freeze. Adam di Carlo assured me that the boot-floppies are just not ready yet, and won't be for a number of weeks even if they get help. Also, the count of release-critical bugs is going back up as fast as it came down. (I think that many of them are not really release-critical, but there are so many that just evaluating them takes a significant amount of time.) I hoped that a week or two of old-style freeze could get potato in shape in time for a mid-December release, but it's just not going to happen. Adam says that the boot-floppies can be ready for freezing on December 1st, and of release-quality on January 1st, and that those dates are somewhat optimistic. I think that freezing on either of those dates is not useful, due to the winter festivities and the end of the world. I'm rescheduling the freeze for mid-January, the weekend of the 15th and 16th. This will be a freeze according to the original plan for potato, with all the pieces ready beforehand and a fast track to a release in February. Please keep this freeze date in mind; don't start anything that you can't finish before that time. In particular, with library upgrades and package reorganizations, keep in mind that other packages will have to be recompiled. I'll ask the archive maintainers to actually hold back such packages starting around December 20th. The good news is that James and I spent a day processing most of Incoming in preparation for the freeze (and I apologize to James for not actually freezing after all that), so the backlog is now gone. In the meantime, the boot-floppies NEED HELP. If you want to get involved, you can check out their code with this command: cvs -d [EMAIL PROTECTED]:/cvs/debian-boot co boot-floppies Make sure that CVS_RSH is set to ssh. The mailing list for coordination is debian-boot; CVS update messages are also sent there. The bug reports are collected under the package name boot-floppies. Richard Braakman
Re: FREEZE RESCHEDULED
Richard Braakman [EMAIL PROTECTED] writes: I was too hasty when declaring this freeze. Adam di Carlo assured me that the boot-floppies are just not ready yet, and won't be for a number of weeks even if they get help. Also, the count of release-critical bugs is going back up as fast as it came down. (I think that many of them are not really release-critical, but there are so many that just evaluating them takes a significant amount of time.) One of the best ways of getting the release-critical bugs under control is to freeze potato. As long as we can upload packages, we will upload bugs. If we freeze now, we can reduce the number of bugs to a reasonable level over the next few weeks. By the time boot-floppies are ready the bug count will be at a manageable level, and potato will be ready for release.
Re: FREEZE RESCHEDULED
On Sun, Nov 07, 1999 at 06:23:44AM -0800, Kevin Dalley wrote: Richard Braakman [EMAIL PROTECTED] writes: I was too hasty when declaring this freeze. Adam di Carlo assured me that the boot-floppies are just not ready yet, and won't be for a number of weeks even if they get help. Also, the count of release-critical bugs is going back up as fast as it came down. (I think that many of them are not really release-critical, but there are so many that just evaluating them takes a significant amount of time.) One of the best ways of getting the release-critical bugs under control is to freeze potato. As long as we can upload packages, we will upload bugs. If we freeze now, we can reduce the number of bugs to a reasonable level over the next few weeks. By the time boot-floppies are ready the bug count will be at a manageable level, and potato will be ready for release. How about a light freeze where we don't accept new packages until the next unstable. Then atleast we don't age the distribution, and we can still upgrade packages, and fix bugs. Ben
Re: FREEZE RESCHEDULED
One of the best ways of getting the release-critical bugs under control is to freeze potato. As long as we can upload packages, we will upload bugs. If we freeze now, we can reduce the number of bugs to a reasonable level over the next few weeks. By the time boot-floppies are ready the bug count will be at a manageable level, and potato will be ready for release. How about a light freeze where we don't accept new packages until the next unstable. Then atleast we don't age the distribution, and we can still upgrade packages, and fix bugs. Every year with the same problems :-) This 'pre-release' will do it if we don't work on the new unstable; this one is only to upload new versions. Regards, Hartmut
