On Wed, Aug 02, 2006 at 02:51:27PM +0200, Frans Pop wrote: > I think this list misses a step: > - package gets built for other architectures by buildds
Good point. It fits in: On Wed, Aug 02, 2006 at 08:32:55PM +1000, Anthony Towns wrote: > 1. Package gets uploaded (queue/unchecked) > 2. Package gets automatically moved to proposed-updates queue (queue/p-u-new) > - viewable via http://ftp-master.debian.org/proposed-updates.html > - accessible by debian-release team > 3. Package gets reviewed and commented upon by debian-release team > - comments viewable via proposed-updates.html page > 4. debian-release team indicates package should be accepted or rejected > - currently via direct communication with ftpmaster > 5. ftpmaster accepts package (queue/accepted) or rejects package > (queue/rejected) > - currently a disgusting hack that doesn't close bugs or send mail > properly > 6. Package gets included in proposed-updates suite (dists/proposed-updates) in > the archive and on mirrors 6.5. Package gets autobuilt, uploaded to queue/unchecked, moved straight into queue/accepted, and from there to proposed-updates in the daily run. > 7. Stable release team issues a point update, and ftpmaster moves contents of > the proposed-updates suite into stable, as well as making other changes > due for the point release Unlike unstable, proposed-updates doesn't get built from incoming (queue/accepted), only when it's actually made it into the archive. Cheers, aj
signature.asc
Description: Digital signature
