Revision 2 as of 2010-05-18 13:00:11

Clear message


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


  • 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


  • 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