Write cron job to e-mail about packages in -proposed

[broder]

We should write something to e-mail us when a package has been in -proposed for more than a day or so so that we don't forget to migrate functional packages to production.

In a perfect world, I think such a script should track which package/version combinations it's already notified us about so we only get notified for a given pair once.

[broder]

This is fixed for any release we still care about

[broder]

Whoops - wrong ticket

[broder]

Mitch mentions as an option that, since different packages spend different amount of times in -proposed, the cron script should have some sense of when a package has been stewing long enough.

One option would be to put something roughly date-like in the keywords field on a ticket, and key off of that.

[quentin]

Why don't we just have the script send a single e-mail once per day to debathena@ if there are any packages in -proposed, showing the number of days each package has been in -proposed and a snippet from the changelog?

[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.

[jdreed]

While this is not the same thing, I have updated package-list.pl to accept a path component of "ctime", which will include the ctimes of the .debs in the repo. (Packages which have a ctime of within 120 seconds of each other are defined as having been created at the same time).

This means that you can use http://debathena.mit.edu/package-list/proposed/ctime to see the creation time of packages in the specified repository. Packages older than 5 days have their ctime in bright red, packages younger than 5 days have it in reddish-brown.

[jdreed]

/mit/debathena/cron_scripts/debathena-nag.pl will be run at 8am each day.

[jdreed]

Well, it successfully ran, but it send mail to me. I've changed it to send mail to debathena-root for now.