UNRKarmicSeeds
2845
Comment:
|
← Revision 5 as of 2009-06-11 07:05:45 ⇥
2646
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
* '''Contributors''': Steve Kowalik * '''Packages affected''': {{{mobile-meta}}}, {{{ubuntu-meta}}} |
* '''Contributors''': Steve Kowalik, Emmet Hikory, Loic Minier * '''Packages affected''': {{{mobile-meta}}}, {{{ubuntu-meta}}}, some infrastructure |
Line 18: | Line 18: |
== User stories == == Assumptions == |
With Ubuntu MID moving to a community flavour, it makes sense to move UNR away from the mobile seed pod into it's own, and to update the tools that have the seed location set. |
Line 24: | Line 22: |
You can have subsections that better describe specific parts of the issue. |
|
Line 28: | Line 24: |
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: | The UNR seed, which is the {{{netbook-remix}}} file, the {{{live}}} file, and {{{STRUCTURE}}}, will be moved from the mobile.karmic bzr branch into a unr.karmic bzr branch. Modulo some Launchpad changes, the task can be named {{{ubuntu-netbook-remix}}}, like the meta package is, and {{{livecd-rootfs}}} updated to install that task. The {{{ubuntu-netbook-remix}}} package will be built from {{{unr-meta}}}. |
Line 40: | Line 40: |
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. |
The cdimage code, unr-meta, and any other places that call germinate will need to be taught about the new location of the UNR seeds. |
Line 47: | Line 44: |
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. |
As long as the meta package is buildable, and the task visible, this should have little to no impact. |
Launchpad Entry: unr-karmic-seeds
Created: 2009-05-20
Contributors: Steve Kowalik, Emmet Hikory, Loic Minier
Packages affected: mobile-meta, ubuntu-meta, some infrastructure
Summary
Currently seeds for UNR are their own seed pod with the MID seed. This specification is to discuss if we should move the UNR seed out, and if so, where to.
Release Note
Not needed, no user-visible changes.
Rationale
With Ubuntu MID moving to a community flavour, it makes sense to move UNR away from the mobile seed pod into it's own, and to update the tools that have the seed location set.
Design
Implementation
The UNR seed, which is the netbook-remix file, the live file, and STRUCTURE, will be moved from the mobile.karmic bzr branch into a unr.karmic bzr branch.
Modulo some Launchpad changes, the task can be named ubuntu-netbook-remix, like the meta package is, and livecd-rootfs updated to install that task.
The ubuntu-netbook-remix package will be built from unr-meta.
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
The cdimage code, unr-meta, and any other places that call germinate will need to be taught about the new location of the UNR seeds.
Test/Demo Plan
As long as the meta package is buildable, and the task visible, this should have little to no impact.
BoF agenda and discussion
- what a seed is? Discussed to bring everyone up to speed
- proposal to break out a new branch
- UNR seeds - other issues How do you test these seeds - there is no user interface to it, it is a plumbing change.
- The concern is about structure
- This is a nice to have - naming, MID specific , more people have access
- If we do split then we can create another seed gtk desktop common. This only makes sense if we create mobile seed.
- loic - Why do we want to split things out?
- Steve,Emmit - Nice to have and ????
- OGR models are different we won't have access to different packages (Main,.... )
- Because of meta pkgs
- Rookery will explode
- 30 pkgs need to included, Check with robbie agree on moving to ubuntu
- find out next step after checking with Robbie
- Open Question -Do we use ubuntu live, or our own live - mobile???
Specs/UNRKarmicSeeds (last edited 2009-06-11 07:05:45 by 14)