[2074] in athena10
Re: proposed
daemon@ATHENA.MIT.EDU (Evan Broder)
Sun Apr 5 11:50:10 2009
Message-ID: <49D8D31C.5010801@mit.edu>
Date: Sun, 05 Apr 2009 11:49:48 -0400
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Evan Broder <broder@mit.edu>
CC: Debathena <debathena@mit.edu>
In-Reply-To: <49D6AFA6.3000200@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Ok - just so that I and everyone else can keep track, here's the
calendar for what's moving into production this week.
4/6:
- delete
- get-message
- lert
- machtype
- pam-config
- reactivate
- mitmailutils (moves to proposed)
- Punt from in proposed when that happens
4/7:
- bugme
- tex-config, assuming it's been tested
- cluster
4/9:
- mutt-config (and clients)
- mitmailutils
- thunderbird-config (moves to proposed)
bugme is a bit of a weird case here. There previously wasn't a set date
for moving it to production. However, debathena-cluster in proposed
depends on bugme, so if we want the cluster machines to pull in
tex-config, bugme has to go to production as well. I'm pretty sure we've
verified at this point that bugme doesn't do anything on
non-quickstations, so I don't see the harm in including a NOOP.
- Evan
Evan Broder wrote:
> machtype, pam-config, and reactivate have fairly straightforward
> changes, and have been sitting around for a while. I'm going to plan to
> move them late Monday.
>
> - Evan
>
