ServerPreInstallation

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2008-11-25 12:49:16 →
Size: 3113
Editor: mx
Comment:
← Revision 4 as of 2009-01-15 19:27:15 → ⇥
Size: 1491
Editor: ppp-70-244-201-45
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
''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.)''
Line 30: Line 29:
You can have subsections that better describe specific parts of the issue.
Line 33: Line 30:

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
Line 38: Line 33:
Should cover changes required to the UI, or specific UI that is required to implement this
Line 41: Line 34:

Code changes should include an overview of what needs to change, and in some cases even the specific details.
Line 46: Line 37:
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.
Line 52: Line 38:

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.

This need not be added or completed until the specification is nearing beta.
Line 59: Line 41:
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.
Line 62: Line 42:

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.

Summary

We should look at the current installation design and remove any questions we can, add anything that we think is missing and have a firm grasp on our overall status.

  • Compare our installation to the current ones by Red Hat and Novell SUSE (Microsoft Windows?)
  • Examine whether our installation meets the common use cases (means specifying them in a specification)
  • Change the installation to meet anything that we are currently missing or over-complicating

Release Note

Rationale

We know that the speed and simplicity of the installation process is key to providing a "Just Works" experience. We want to offer the best default configuration we can, and offer the ability to set-up optional pieces (tasks), so we must balance these two areas. We firmly do not want a second stage after the installer has run. We should look at the current installation design and remove any questions we can, add anything that we think is missing and have a firm grasp on our overall status.

Use Cases

Assumptions

Design

Implementation

UI Changes

Code Changes

Migration

Test/Demo Plan

Unresolved issues

BoF agenda and discussion

CategorySpec

ServerPreInstallation (last edited 2009-02-19 16:01:08 by 82-69-40-219)