[7420] in Release_7.7_team
Re: cluster-cups-config
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Tue Mar 22 04:17:23 2011
Date: Tue, 22 Mar 2011 04:17:16 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
cc: "release-team@mit.edu Team" <release-team@mit.edu>
In-Reply-To: <DB71AD22-14DB-4B3C-BCDD-70CFE862A82A@mit.edu>
Message-ID: <alpine.DEB.2.00.1103220410530.21147@lunatique.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
I can't test things over spring break, given that as far as I know there
are no cluster machines nor Athena printers in California, but the code
changes for both 2.0 and 2.0.1 are fine, so I approve of pushing this
provided someone (you?) has tested it.
I am unhappy that cluster-cups-config hard-codes the Athena printer list,
but I've been unhappy about this since basically when the package isn't
created, so this isn't an objection. Probably the right long-term answer
is to query something on the order of Hesiod for a list of cluster
printers and regen printers.conf out of that, but in the absence of
someone writing such code, I don't think there's any harm in pushing
changes to cluster-cups-config that just affect the list of printers
immediately after testing, since it's not really a code change.
(I don't see a whole lot of advantage in "testing" a non-live Pharos
printer three business days before it becomes Pharos, unless I
misunderstand that deployment process. Assuming we do care about testing,
we should test the configuration we care about, i.e., after the printer is
Pharos.)
--
Geoffrey Thomas
geofft@mit.edu
On Mon, 21 Mar 2011, Jonathan Reed wrote:
> 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
>
>
