Consider performing a - Ftp-master 10 UTC (1.5h - 2h)
- disable cronjobs
stable -> oldstable
testing -> stable
- (parallel with later tasks) security archive
d-i RM (> 0.5h)
- verify state of the archive (including lenny-r0)
RM (> 0.5 h)
- disable cronjobs
- verify state of the archive and sign
- w-b admins (in parallel)
- disable cronjobs
- suite rollover
- Mirror team
- sync archive and verify (in 2 stages: first kassia/farbror, rest afterwards)
cd team + live team (> 4h)
- build images and verify
- images on cdimage and verify
- Mirror team
- sync cdimage and verify? (15 mins from the cds being "known good", mirrors take 2 hours to 2 days to sync from experience)
- DSA + others
- seeding torrents and verify (torrents can overlap testing, but risk early publication, 0.5 h for "hot" torrents, 3h for all torrents)
- webmaster
- tag for releases
- trigger rebuild website
- press team ( About 30 min to send out the announcement after cds are available; website needs to be triggered manually)
- announcement (mail and web)
- reactivate cronjobs?
- RM (in parallel)
- Thank you mail
- buildd admins (in parallel)
- build chroots rollover
