ARMDeveloperEnvironment

Differences between revisions 1 and 6 (spanning 5 versions)
Revision 1 as of 2010-04-27 15:23:45
Size: 2620
Editor: fw-unat
Comment:
Revision 6 as of 2010-05-19 14:16:25
Size: 5052
Editor: bd7a3fd5
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * '''Launchpad Entry''': [[https://blueprints.launchpad.net/ubuntu-arm/+spec/arm-m-dev-env]]  * '''Launchpad Entry''': [[https://blueprints.launchpad.net/ubuntu-arm/+spec/arm-m-development-tools]]
Line 5: Line 5:
 * '''Contributors''':  * '''Contributors''': GuilhermeSalgado
Line 10: Line 10:
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.  * provide a way to create new archives by branching a subset of ubuntu packages
 * make it easy to change these archives
 * manage deltas between archives and their (direct or no?) parents

Not sure if the distinction between full/slim archives is pertinent here? I
mean, what type of archives would we be creating? AIUI, we need to create a
full archive when the child archive includes toolchain changes that would
break binary compatibility?
Line 14: Line 21:
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.
-
Line 20: Line 24:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. We need to allow ARM developers to easily create/maintain derivative archives for use during the development of new devices. They should be able to branch archives, make changes to them and manage deltas.
Line 24: Line 28:
 * Ted wants to package the latest version of the Foo project, which depends on the latest version of Bar and Baz, which in turn are not yet available in Ubuntu. Instead of packaging Bar and Baz, Joe can branch off of two existing PPAs that already have packages for the latest version of Bar and Baz. (This use case was invented to try and explain why we might want multiple parents, as discussed during the UDS session)

 * A partner is developing a custom netbook UI but need to keep it private until it's finalized, so they create a slim archive off of the main Ubuntu archive and do any UI changes (or add new packages) on their new archive, which is only accessible by themselves. The slim archive is made possible (instead of a full one) because it should be binary compatible with the main Ubuntu archive. (Not yet clear whether or not the new archive should be hosted on LP, like a private PPA; probably need to allow it to live in LP or outside)

 * YAP (Yet Another Partner) is working on optimizing their new (not-yet-released) chip, but for that they need a version of GCC newer than the one on the Ubuntu archive. They want to create a new (private) archive where they'll upload the new GCC version, but upgrading to that new version of GCC is known to break binary compatibility, so it must be possible for them to easily rebuild all packages using the new GCC.

Is https://wiki.ubuntu.com/Specs/M/DerivedArchiveRebuild related to this in
any way?
Line 25: Line 38:

 * archives can be refered to by their URLs. (I think this is how we're going to tell the tools the archives they'll operate on.
Line 42: Line 57:
=== 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.
Line 60: Line 68:

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.
=== Goals ===
 * Goal: branch subset of ubuntu packages and manage changes
  * experiments - short/adhoc / long running
  * multiple parents: e.g. integrate goodies from multiple PPAs
  * hierarchy: common archive -> project archive -> project variant archive etc.
   * automatic superseding and merging
=== Releasing ===
 * Release/Freezes/ACLs
   * have automatic merged release branch owned by releaes team during development
     period that gets set to manual mode during freezes.
   * at release another branch is auto created that is not changeable??
=== Getting Started ===
 * getting started: command line tool to branch some archive; by default it starts
   by copying the binaries;
 * managing changes: webtool that visualizes relationship to parent archive:
   * changes in downstream archive
  * changes in upstream archive (merge o matic'ish)
 * some changes like gcc would require move a binary copy archive to a source/rebuild
   everything mode? is that true? gcc might just have changed for a bug fix/crash etc.
   * tracking build dependencies may be relevant here
 * a way of enforcing version number rules in a particular archive would be good

Summary

  • provide a way to create new archives by branching a subset of ubuntu packages
  • make it easy to change these archives
  • manage deltas between archives and their (direct or no?) parents

Not sure if the distinction between full/slim archives is pertinent here? I mean, what type of archives would we be creating? AIUI, we need to create a full archive when the child archive includes toolchain changes that would break binary compatibility?

Release Note

-

Rationale

We need to allow ARM developers to easily create/maintain derivative archives for use during the development of new devices. They should be able to branch archives, make changes to them and manage deltas.

User stories

  • Ted wants to package the latest version of the Foo project, which depends on the latest version of Bar and Baz, which in turn are not yet available in Ubuntu. Instead of packaging Bar and Baz, Joe can branch off of two existing PPAs that already have packages for the latest version of Bar and Baz. (This use case was invented to try and explain why we might want multiple parents, as discussed during the UDS session)
  • A partner is developing a custom netbook UI but need to keep it private until it's finalized, so they create a slim archive off of the main Ubuntu archive and do any UI changes (or add new packages) on their new archive, which is only accessible by themselves. The slim archive is made possible (instead of a full one) because it should be binary compatible with the main Ubuntu archive. (Not yet clear whether or not the new archive should be hosted on LP, like a private PPA; probably need to allow it to live in LP or outside)
  • YAP (Yet Another Partner) is working on optimizing their new (not-yet-released) chip, but for that they need a version of GCC newer than the one on the Ubuntu archive. They want to create a new (private) archive where they'll upload the new GCC version, but upgrading to that new version of GCC is known to break binary compatibility, so it must be possible for them to easily rebuild all packages using the new GCC.

Is https://wiki.ubuntu.com/Specs/M/DerivedArchiveRebuild related to this in any way?

Assumptions

  • archives can be refered to by their URLs. (I think this is how we're going to tell the tools the archives they'll operate on.

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.

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

Goals

  • Goal: branch subset of ubuntu packages and manage changes
    • experiments - short/adhoc / long running
    • multiple parents: e.g. integrate goodies from multiple PPAs
    • hierarchy: common archive -> project archive -> project variant archive etc.

      • automatic superseding and merging

Releasing

  • Release/Freezes/ACLs
    • have automatic merged release branch owned by releaes team during development
      • period that gets set to manual mode during freezes.
    • at release another branch is auto created that is not changeable??

Getting Started

  • getting started: command line tool to branch some archive; by default it starts
    • by copying the binaries;
  • managing changes: webtool that visualizes relationship to parent archive:
    • changes in downstream archive
    • changes in upstream archive (merge o matic'ish)
  • some changes like gcc would require move a binary copy archive to a source/rebuild
    • everything mode? is that true? gcc might just have changed for a bug fix/crash etc.
    • tracking build dependencies may be relevant here
  • a way of enforcing version number rules in a particular archive would be good


CategorySpec

Specs/M/ARMDeveloperEnvironment (last edited 2010-06-08 10:57:12 by fw-unat)