[7419] in Release_7.7_team
cluster-cups-config
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Mon Mar 21 22:24:45 2011
From: Jonathan Reed <jdreed@MIT.EDU>
Content-Type: text/plain; charset=us-ascii
Date: Mon, 21 Mar 2011 22:24:38 -0400
Message-Id: <DB71AD22-14DB-4B3C-BCDD-70CFE862A82A@mit.edu>
To: "release-team@mit.edu Team" <release-team@mit.edu>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Transfer-Encoding: 8bit
Oliver has ACK'd cluster-cups-config 2.0.1 (in -development). I just pushed it to proposed.
I'd like to ask for an exception to the workflow process for cluster-cups-config 2.0.1, for the following reasons:
- cluster-cups-config 2.0 (the version which adds printers using add-athena-printer and lpadmin, and stops shipping config files) has been in proposed for a week and has been tested.
- The only changes 2.0.1 makes are to add "-f" to add-athena-printer (to clobber existing queues of the same name - remember, this is cluster only, so clobbering existing Athena queues is fine) and to add "wired" (N42) as a Pharos printer.
- It's Spring Break, and usage is minimal
If nobody objects by tomorrow (Tue) at 5, I'm going to assume that there are no objections.
Going forward, I'd also like to ask for a blanket exception to the workflow process for cluster-cups-config between now and the Natty release, as new Pharos printers will be coming online, and we'll need to stay current. I'm going to work with CopyTech to ensure we get at least 3 business days notice of new Pharos printers, and given that, I'd like to suggest that builds of cluster-cups-config need only one test on a cluster machine by the original developer, and can then go to proposed.
Feedback?
-Jon
