InstallUpdatesWhenInstallingUbuntu
Launchpad Entry: foo
Created:
Contributors:
Packages affected:
Summary
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.
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
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.
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:
- 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.
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
Preseedable option for Dell. Move the language pack download in this, moved earlier than 80%. Actual language pack installing still happens later. We don't want a progress meter because we don't want to make the user think they have to wait for the updates to finish downloading. Put as a checkbox on the summary page or the advanced page instead of having a cancel button? - AU problem. GEOIP would let us select a good timezone point and a good local mirror, somewhat limiting the AU problem, though we'd still want to let them disable this download somehow. Offer a checkbox that's checked by default and says "Download updates while installing" that sits just below the install progress. You would have to act quickly if you wanted to uncheck the box. - We can wait a few seconds, or after partitioning to start. We may want to explicitly not offer this option at all when on 3G. - PackageKit as an example. - Default the checkbox as off in this case? - Colin to talk to Michael Fragmentation a problem? - "Let the filesystem sort it out" - We do lots of things at the same time, this is not an issue. Measure how often people are using this? - Change user-agent. Announce during milestone, doing this, what do you think? Colin thinks it will need more than a preseed. We disable update-notifier on the live cd. Not start the download until we're at copying files. Disable the checkbox if NM reports no network connection. Use subprocess and send SIGTERM to it when done.
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.