Future Release Infrastructure
As we move towards new markets and challenges to satisfy those markets, its time to re-examine how we've been doing things, and start planning for the longer term infrastructure goals we want to have in place for the next LTS and beyond. The build infrastructure has evolved since it was started 8 years ago, and several things work very well, while others could benefit from some brainstorming about what we'd do if we had a clean slate.
Blueprint information
- Status:
- Started
- Approver:
- Steve Langasek
- Priority:
- High
- Drafter:
- Kate Stewart
- Direction:
- Approved
- Assignee:
- Ubuntu Release Team
- Definition:
- Approved
- Series goal:
- Accepted for raring
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Steve Langasek
- Completed by
Whiteboard
This is a discussion session to start the brainstorming about a roadmap to evolve our release infrastructure to be better able to support: servers, embedded devices, 100x users.
Questions for the discussion:
What are the release requirements these new markets are going to need to enable us to participate in them?
If we had a clean slate to start from, what would an ideal archive, build infrastructure, tools, methodology look like?
Do our current milestones and freeze windows, fit new requirements?
Do we have redundancy and flexibility to be able to adapt and react?
How do we remove the manual bits of release process and make it more robust?
Work Items
Work items for ubuntu-
[cjwatson] rewrite publish-release in python with unittests: DONE
Work items for ubuntu-
[stgraber] Add "rebuild" flag to the tracker so nusakan can get a list of pending rebuilds, product leads can ask for rebuilds and we can track the state of all of that: TODO
Work items:
[adconrad] turn pad pipelines and crontab into some scripts (and pull image list into etc/): TODO
[adconrad] implement 'rebuild-all-images --contains ubiquity (or was it ubiquity >= 1.2.3.4?): TODO
[adconrad] summarize hardware bottlenecks are in existing release process: TODO
[stgraber] Help Ben Howard to setup automated posting to QA tracker for cloud images: DONE
[stgraber] Push chinese to localized tracker automatically: DONE
[stgraber] Generate https:/
[stgraber] Improve visiblity of milestone status on the tracker. Make it easier to access archived milestones and offer a series view with a dedicated URL: DONE
Dependency tree
* Blueprints in grey have been implemented.
