KubuntuHardyKde4

Differences between revisions 4 and 5
Revision 4 as of 2007-10-24 11:15:10
Size: 2540
Editor: 87-194-29-91
Comment:
Revision 5 as of 2007-11-02 14:26:19
Size: 2413
Editor: 12
Comment:
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
You can have subsections that better describe specific parts of the issue. Merge with Debian, keep packages co-installable and move kdeedu to main.,
Line 33: Line 33:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: Merge with Debian
Line 35: Line 35:
=== UI Changes === keep installed into /usr/lib/kde4
Line 37: Line 37:
Should cover changes required to the UI, or specific UI that is required to implement this have the packaging create wrapper scripts for each binary in /usr/bin/<binary>-kde4 which export required PATHs and run /usr/lib/kde4/<binary>. Also create menu entries in /usr/share/applications/<binary>-kde4 which point to /usr/lib/kde4/<binary>-kde4
Line 39: Line 39:
=== Code Changes === binary packages need to be renamed to <package>-kde4 if they overlap in name
Line 41: Line 41:
Code changes should include an overview of what needs to change, and in some cases even the specific details. Make sure kdebase-data and kdelibs5, kdebase-runtime-bin, kdebase-runtime-data, kde-icon-oxygen are coinstallable under both kde3 and kde4 in order to support the items athat are in main (kde-edu)

move these into /usr/ and put them into main w/ kde-edu along with kde-games

ensure front-end tools get created for packagekit. This is not a requirement for hardy but should be started in its timeframe to ensure they are ready for hardy+1.

== CDs ==

uni-distro as the script and include as much as can fit on the CD
upload to Kubuntu.org
for each release of kde4 build a CD
built on Gutsy until Hardy releases then build on Hardy

.
Line 45: Line 58:
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.
None at this stage, continue to use ~/.kde4 for data. Move to ~/,.kde for hardy+1
Line 50: Line 60:
== 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 CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

== Outstanding 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 ==

Handle the 4.0 release, merge with Debian and get it in sync with Ubuntu features.

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

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.

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.

Use Cases

Assumptions

Design

Merge with Debian, keep packages co-installable and move kdeedu to main.,

Implementation

Merge with Debian

keep installed into /usr/lib/kde4

have the packaging create wrapper scripts for each binary in /usr/bin/<binary>-kde4 which export required PATHs and run /usr/lib/kde4/<binary>. Also create menu entries in /usr/share/applications/<binary>-kde4 which point to /usr/lib/kde4/<binary>-kde4

binary packages need to be renamed to <package>-kde4 if they overlap in name

Make sure kdebase-data and kdelibs5, kdebase-runtime-bin, kdebase-runtime-data, kde-icon-oxygen are coinstallable under both kde3 and kde4 in order to support the items athat are in main (kde-edu)

move these into /usr/ and put them into main w/ kde-edu along with kde-games

ensure front-end tools get created for packagekit. This is not a requirement for hardy but should be started in its timeframe to ensure they are ready for hardy+1.

== CDs ==

uni-distro as the script and include as much as can fit on the CD upload to Kubuntu.org for each release of kde4 build a CD built on Gutsy until Hardy releases then build on Hardy

.

Migration

None at this stage, continue to use ~/.kde4 for data. Move to ~/,.kde for hardy+1


CategorySpec

KubuntuHardyKde4 (last edited 2008-08-06 16:32:39 by localhost)