[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

why is alpha a release candidate?

So the release criteria require buildd redundancy.  And yet, half the
release candidate archs still don't have it.  It gets marked in yellow
on http://release.debian.org/etch_arch_qualify.html.

Well, the one-and-only alpha buildd has been down for apparently ten
days and does not respond to ping, and I don't recall seeing anything
from the alpha team on debian-release or debian-devel.  Please correct
me if this is inaccurate.

It seems to me that, in a freeze, we should be ruthless about such a
situation.  We have in the past had serious problems with archs that
have suddenly-bogus buildds in the freeze, and this requirement of
buildd redundancy was created specifically to avoid this problem.  Now
we are being bitten by it.

Alpha needs to either, it seems to me, get back up to 95% right away,
and say why the situation was allowed to coast along for nearly two
weeks, or be dropped as a release arch.  

Or, we could just decide that the release criteria don't really matter,
even when the very situations they were designed to prevent come up.


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: