Differences between revisions 5 and 6
Revision 5 as of 2009-11-18 22:12:51
Size: 3715
Editor: 63
Revision 6 as of 2009-11-19 15:55:20
Size: 3785
Editor: 63
Deletions are marked like this. Additions are marked like this.
Line 67: Line 67:
 * General server seeds review  * Look at the delta between hardy and karmic
 * General server seeds review / server package set
Line 69: Line 70:


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.


This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

User stories



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:

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.



  • 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 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

  • Canonical application support (server-lucid-canonical-application-support) -mdz

  • Update autofs4 to autofs5? -mdz
  • Cluster stack (server-lucid-cluster-stack) -mdz

  • sysstat package be shipped with Ubuntu Server - jsalisbury
  • oprofile and systemtap package be shipped to provide deeper performance analysis. -jsalisbury
  • I'd like to request that virt-manager be dropped from Main to Universe. It ships on the DVD, but not the other installable media. Most all virt-manager users have to apt-get install it post installation anyway. From a maintainability standpoint, no core-developer is really looking after the package. It falls outside of the scope of the Server team, since it's a GUI/desktop package, but no one from the Desktop team is looking after it either. The interface is years and years behind the interface of VirtualBox. And the bug backlog is huge. I suggest that virt-manager be dropped from the Main seeds, to Universe, for Lucid. -- DustinKirkland

  • Look at the delta between hardy and karmic
  • General server seeds review / server package set
  • Look into dvd seed for server packages (time permitting)

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.


LucidServerSeeds (last edited 2010-02-17 18:59:09 by dsl-173-206-1-210)