Design a system for frequent and predictable archive rebuilds

Registered by Adam Conrad on 2006-06-09

This spec will probably be a combined Ubuntu/Launchpad spec (TBD in discussion in Paris, I suspect), focussing on how to move autotesting from a horrible hack that makes elmo cry and takes ages to set up and get rolling to something a bit more elegant that "just works" and can be done on a reliably predictive schedule.

Blueprint information

Status:
Not started
Approver:
Matt Zimmerman
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items