KernelMaverickConfigReview

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2010-04-12 22:42:29 →
Size: 2593
Editor: c-76-105-148-120
Comment:
← Revision 2 as of 2010-04-15 16:44:28 → ⇥
Size: 1956
Editor: c-76-105-148-120
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:

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.		 Review of the kernel configuration for Maverick. This will concentrate on confirming the policy for various option type, as well as new options. For major new options, discussion and confirmation of the selection of each.
Line 13: Line 12:

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.		 TBC
Line 19: Line 15:
We need to review the Maverick kernel config to:
Line 20: Line 17:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

== User stories ==

== Assumptions ==

== Design ==

You can have subsections that better describe specific parts of the issue.		  * Ensure sanity of options we have enabled/disabled
 * Ensure that we have the best possible coverage for hardware
 * Ensure we maintain our security options
Line 31: Line 22:
We need to review the default selection criteria for new options. We need to review any new options to ensure they are sensibly set. Finally we need to review important options such as filesystem selections and security options to ensure they are set as expected.
Line 32: Line 24:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: === Selection Criteria ===
Line 34: Line 26:
=== UI Changes === The basic rules are:
Line 36: Line 28:
Should cover changes required to the UI, or specific UI that is required to implement this  1. if the option may be selected as module then we will enable it as a module,
 1. if the option creates a new subsystem (or filesystem) we will enable it,
 1. if the option is unlikely to cause regressions to existing behaviour we will enable it,
 1. else it will be disabled.
Line 38: Line 33:
=== Code Changes === Additionally we have general policy of building in:
Line 40: Line 35:
Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

Include:
 * 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.

== 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.		  1. subsystems associated with busses (as they will probe much earlier that way)
 1. boot essential subsystems
 1. default filesystems

Summary

Review of the kernel configuration for Maverick. This will concentrate on confirming the policy for various option type, as well as new options. For major new options, discussion and confirmation of the selection of each.

Release Note

TBC

Rationale

We need to review the Maverick kernel config to:

  • Ensure sanity of options we have enabled/disabled
  • Ensure that we have the best possible coverage for hardware
  • Ensure we maintain our security options

Implementation

We need to review the default selection criteria for new options. We need to review any new options to ensure they are sensibly set. Finally we need to review important options such as filesystem selections and security options to ensure they are set as expected.

Selection Criteria

The basic rules are:

  1. if the option may be selected as module then we will enable it as a module,
  2. if the option creates a new subsystem (or filesystem) we will enable it,
  3. if the option is unlikely to cause regressions to existing behaviour we will enable it,
  4. else it will be disabled.

Additionally we have general policy of building in:

  1. subsystems associated with busses (as they will probe much earlier that way)
  2. boot essential subsystems
  3. default filesystems

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

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.

CategorySpec

KernelTeam/Specs/KernelMaverickConfigReview (last edited 2010-05-25 00:57:46 by c-76-105-148-120)