Summary

Continuing on the work we have completed in previous blueprints, I'd like for this session to focus on what can be done to continue our efforts in making bugs and bug work more of a fixed priority for the team as well as determining what changes can be made to our current method of determining the bugs to be put on the Top 50 list. We'll also review the utility of the Top 50 and gather ideas on improvements there should that process be seen as effective.

Release Note

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.

Rationale

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

Test/Demo Plan

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.

Unresolved issues

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

https://wiki.ubuntu.com/KernelTeam/Specs/OtherKernelNBugHandling

* Bugs with patches

* More productive bug lists

* kerneloops reports

* Update wiki docs to reflect new processes

Regression types have been reviewed and now we have regression-release, -proposed, -updates + a tag with the version the regression has been found in and nomination of the affected releases.

ACTIONS

See blueprint whiteboard for actions.


CategorySpec

KernelTeam/Specs/OtherKernelNBugHandling (last edited 2010-11-04 16:21:51 by apw)