Better coordinating when pages update?
So, http://bugs.debian.org/release-critical/other/all.html
and http://packages.qa.debian.org/
and http://bts.turmzimmer.net/
all show packages as being in 'testing' which aren't, because they were
removed on the last run.
Perhaps there's some way to schedule the (apparently daily) update of these
so that it happens shortly *after* the testing scripts run?
(Shortly after the unstable installation scripts run would be good too.)
I don't really know what the timing on these things is, but it seems to me
this wouldn't be too hard if the timing information was available, and
would result in improved accuracy at little cost.
--
Make sure your vote will count.
http://www.verifiedvoting.org/
Reply to: