On Wed, Aug 02, 2006 at 10:50:25AM +0200, Lo?c Minier wrote:
> On Wed, Aug 02, 2006, Martin Zobel-Helas wrote:
> > for those who wonder why their package did not yet hit proposed-updates,
> > they want to have a look on [1] and [2].
> I don't quite understand the various steps that a package traverses
> when uploaded to SPU. Is some document explaining that? In short, I
> would just like to understand the number of steps, the human-triggered
> transitions, and the public visibility, for example:
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
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
This is still in the process of being properly automated, sadly --
particularly points (4), (5) and (7). :-/
> The page you pointed at seems the
> good resource, but I'm not sure of the process stable uploads exactly
> follow internally.
Hope this helps.
Cheers,
aj
Attachment:
signature.asc
Description: Digital signature