BlueprintHowto
At the beginning of every release cycle, we try to create a road map to document the work needed for the next cycle. The work is divided into what we call blueprints and each blueprint is then discussed at UDS. Below is an outline of how to create a blueprint.
Create a Blueprint in Launchpad
A listing of all Ubuntu blueprints can be seen at: https://blueprints.launchpad.net/ubuntu
To add a new blue print just click on the Register a blueprint link. Then fill out each of the input fields keeping the following things in mind:
Name |
For the Ubuntu Kernel Team, we typically try to name all of our blueprints with the same prefix. The naming convention is usually, kernel-<release>-<short description>. For example, for the Lucid release cycle, we used kernel-lucid-bug-handling for the blueprint that focused on how we were going to improve or bug management. |
Title |
Short descriptive title of the blueprint |
Specification URL |
This is a link to the spec for the blueprint. The spec is a wiki page which is created to outline the rationale for needing this work and how the design, implementation, and testing will be carried out. Each spec follows the same template. For the Ubuntu Kernel Team we usually create all our specs under http://wiki.ubuntu.com/KernelTeam/Specs/ . At a minimum, create the spec based on the template as a placeholder. After discussion takes place at UDS, the drafter/assignee will be responsible to go back and fill in each section of the spec. |
Summary |
Short description of what the rationale behind the spec is and what we hope to accomplish |
Definition Status |
This is initially set to "New". It's set to "Drafting" once the drater/assignee has began drafting the spec. It's set to "Review" when the spec is fully drafted and ready for review. It's set to "Pending Approval" if there are some fixups/changes required of the spec. Finally, it's set to "Approved" when the spec/blueprint is ready to have work started. |
Assignee |
Person responsible for completing the spec/blueprint |
Drafter |
Person responsible for taking notes on the discussion at UDS and also for drafting the spec |
Approver |
Person responsible for approving the spec - usually your manager |
Propose for sprint |
Set to the release this is targeted for |