[6543] in Release_7.7_team
Move early-linux into proposed?
daemon@ATHENA.MIT.EDU (Evan Broder)
Thu Dec 3 15:59:04 2009
MIME-Version: 1.0
Date: Thu, 3 Dec 2009 15:58:55 -0500
Message-ID: <2706d8dd0912031258q7c71e8d7r962b4aa595d9cb2c@mail.gmail.com>
From: Evan Broder <broder@MIT.EDU>
To: release-team@mit.edu
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Flag: NO
X-Spam-Score: 0.00
Can we move the early-linux cluster into -proposed instead of production?
Right now we have a very small handful of machines pulling updates
from -proposed. Many of that very small handful aren't even regularly
used, and fewer are cluster machines. I think it would be useful to
expose -proposed to a wider array of machines, hopefully so that we
can more effectively catch bugs before they get pushed to production.
Also, this would allow us to tell users to go check a particular
machine to see if we've successfully fixed their bug.
You can see the list of machines in early-linux by running `qy -s -f
machine gmcm '*' early-linux` (I won't spew the output at you).
Currently there are a handful of private machines that we should
possibly remove, and only a handful of cluster machines. I think we
should add to early-linux roughly the set of machines that
participated in the Debathena Beta deployment (so a few in m12 and a
few in m56).
This obviously introduces the danger of needing a runaround if we
incapacitate the machines, but uh...hopefully we can avoid that? In
any case, it's pretty easy to hit w20, m12, and m56 if we need to.
Opinions?
- Evan
