Revision 1 as of 2009-05-26 20:50:59

Clear message
  • Launchpad Entry: foo

  • Created:

  • Contributors:

  • Packages affected:


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



We will update the installation testing procedure for KDE to include contempory problems such as network and bluetooth etc. Network management should be at the top of the testing procedure since network is needed for most extra work. We will package other network backends to offer alternatives incase network manager doesn't work for some network setups.

It should be possible to upgrade from Hardy to all distro versions up to the next LTS. Although Kubuntu is not LTS we will have users who have KDE packages installed and want to upgrade. The ISO testing website should add test cases for upgrade from hardy as well as the previous version.

We will write a plasma applet to distribute on out beta installs which will ask questions for structured feedback on areas where we often revieve little feedback, notably translations and bluetooth. This should send an e-mail to an address in a structured format so it can be easily parsed and viewed.