[1707] in athena10
Re: [Debathena] #128: Write cron job to e-mail about packages in
daemon@ATHENA.MIT.EDU (Debathena Trac)
Mon Mar 16 01:25:55 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: broder@mit.edu, quentin@mit.edu, mitchb@mit.edu
Date: Mon, 16 Mar 2009 05:24:17 -0000
Reply-To:
Message-ID: <052.8ff1dcd0f6d4b4051cbd60564e8e85d2@mit.edu>
In-Reply-To: <043.b5912b6699fa4369a590bf562fc06d81@mit.edu>
Content-Transfer-Encoding: 8bit
#128: Write cron job to e-mail about packages in -proposed------------------------+---------------------------------------------------
Reporter: broder | Owner:
Type: enhancement | Status: new
Priority: major | Resolution:
Keywords: aptrepo |
------------------------+---------------------------------------------------
Comment(by mitchb):
The reason for my suggestion is that it's already the case that you guys
have an
idea of how long you want various packages to be tested before putting
them
into production (this is what Evan's been indicating in the text of
tickets
lately). If you get a daily list of everything in -proposed, you'll get
used to
ignoring this piece of automated mail like so many others that mostly
notes
things you don't have to take action on (because you'll usually see
packages
that should still be in -proposed).
If you can tell this script when you intend to deploy packages, its mail
can
usually be relevant because it'll only mail you when a package's stay in
-proposed
should be over. I suspect people will be less likely to instinctively
ignore
the mail then.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/128#comment:6>Debathena <http://debathena.mit.edu/>MIT Debian-Athena Project
