+queue/approved
+--------------
+
+ o What to do with multi-suite uploads? Presumably hold in unapproved
+ and warn? Or what? Can't accept just for unstable or reject just
+ from stable.
+
+ o Whenever we check for anything in accepted we also need to check in
+ unapproved.
+
+ o non-sourceful uploads should go straight through if they have
+ source in accepted or the archive.
+
+ o security uploads on auric should be pre-approved.
+
+
+Others
+------
+
+ o the lockfile (Archive_Maintenance_In_Progress) should probably be in a conf file
+
+ o madison should cross-check the b.source field and if it's not null
+ and s.name linked from it != the source given in
+ -S/--source-and-binary ignore.
+
+ o lauren sucks; she should a) only spam d-i for sourceful
+ rejections, b) sort stuff so she rejects sourceful stuff first. the
+ non-sourceful should probably get a form mail, c) automate the
+ non-sourceful stuff (see b).
+
+ o jennifer should do q-d stuff for faster AA [ryan]
+
+ o split the morgue into source and binary so binaries can be purged first!
+
+ o per-architecture priorities for things like different arch'es
+ gcc's, silly BSD libftw, palo, etc.
+
+ o use postgres 7.2's built-in stat features to figure out how indices are used etc.
+
+ o neve shouldn't be using location, she should run down suites instead
+
+ o halle needs to know about udebs
+
+ o by default hamstring katie's mail sending so that she won't send
+ anything until someone edits a script; she's been used far too
+ much to send spam atm :(
+
+ o $ftpdir/indices isn't created by rose because it's not in katie.conf
+
+ o sanity check depends/recommends/suggests too? in fact for any
+ empty field?
+
+[minor] kelly's copychanges, copykatie handling sucks, the per-suite
+ thing is static for all packages, so work out in advance dummy.
+
+[madison] # filenames ?
+[madison] # maintainer, component, install date (source only?), fingerprint?