* Brian Nelson ([EMAIL PROTECTED]) [041210 19:55]: > Yup. There's never been a sense of urgency. The RM's throw out release > dates and goals every once in a while, but no one seems to take those > seriously.
Not true. (And, perhaps you noticed, the release team avoided to give specific days in the last time, and the timeline depends on a day N.) > And probably for good reason. Remarks like this _are_ driving the release back. > For the second straight > release, when we've gotten to a point that it seemed we were nearly > ready for a release, we then discover we have no security autobuilders. > The release then gets pushed back a few more months, while the plebeian > developers sit around twiddling their thumbs unable to help wondering > why the hell no one thought to set up the autobuilders in the 2+ years > we've been preparing a release. Be assured, the setting up the security autobuilders are a topic since I'm following the process of releasing sarge closely. Like e.g. in http://lists.debian.org/debian-devel-announce/2004/08/msg00003.html which tells us that we need them for being able to freeze. Or, a bit later, http://lists.debian.org/debian-devel-announce/2004/09/msg00005.html. This even tells: | The bad news is that we still do not have an ETA for the | testing-security autobuilders to be functional. This continues to be | the major blocker for proceeding with the freeze I don't think this mean that we suddenly discover it, but as other issues were more prominently blockers e.g. in July (like the toolchain), those issues were resolved back in September (and are still resolved now). Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
