[6081] in Release_7.7_team
Re: Decisions from Athena Release Team.
daemon@ATHENA.MIT.EDU (Evan Broder)
Wed Nov 5 17:33:27 2008
Message-ID: <49121F05.8010606@mit.edu>
Date: Wed, 05 Nov 2008 17:32:37 -0500
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Bill Cattey <wdc@mit.edu>
CC: athena10@mit.edu, release-team@mit.edu
In-Reply-To: <1225926302.2950.98.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Flag: NO
X-Spam-Score: 0.00
Bill Cattey wrote:
> The Athena10 package mirror (not yet in existence), normally takes all
> upstream changes automatically. During a blackout period between drop
> date and the end of Final Exams, only explicitly chosen changes are
> brought over.
>
You're referring to the mirror that cluster machines will use for both
Ubuntu and Debathena packages? I'd be careful about this - you almost
certainly want to take, say, security updates as quickly as possibly.
That shouldn't be too hard, though, since they're separated from
non-security updates, just something to mention and keep in mind.
> "Workstation" is pointed at the IS&T Athena10 mirror, so it will get
> blackouts.
>
Just to be sure we're straight on terminology, you're referring to
debathena-workstation machines as opposed to debathena-cluster? I
strongly disagree with this - the idea of post-drop-date blackouts is
something that's very Athena-specific and not something that I think
should be imposed on non-cluster machines. I'd put it specifically in
the debathena-auto-update package, but even that I'm not entirely sure
of, because I've considered installing debathena-auto-update on my
machines, but wouldn't if it was going to block me from taking /any/
updates.
- Evan
