"Use cases" should be "User stories" (see Wikipedia for more info)
|Deletions are marked like this.||Additions are marked like this.|
|Line 10:||Line 10:|
|This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.||Karmic and Lucid are both supported on the OMAP3 beagleBoard. Maverick should also be ported to the platform.|
|Line 20:||Line 20:|
|This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.||The rational behind the activity is to offer continuity and support for the platform.|
Launchpad Entry: foo
Karmic and Lucid are both supported on the OMAP3 beagleBoard. Maverick should also be ported to the platform.
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
It is mandatory.
The rational behind the activity is to offer continuity and support for the platform.
You can have subsections that better describe specific parts of the issue.
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Should cover changes required to the UI, or specific UI that is required to implement this
Code changes should include an overview of what needs to change, and in some cases even the specific details.
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.