Differences between revisions 2 and 3
Revision 2 as of 2011-11-18 11:38:49
Size: 5264
Editor: cjwatson
Revision 3 as of 2011-11-18 11:43:30
Size: 5017
Editor: cjwatson
Deletions are marked like this. Additions are marked like this.
Line 78: Line 78: the new version though maybe not as useful the new version though maybe not as useful
Line 102: Line 102:

Work items:
[] Take over and update the weather report
[broder] Set up lintian lab: DONE
[] Set up piuparts
[] Generate separate report from lintian of Ubuntu-specific packages
[] Generate JSON output from lintian/piuparts for harvest


We have many reports that help us keep track of automatically-detectable problems in the development release (FTBFS, NBS, component-mismatches, the conflict checker, the transition tracker, etc.). These are all well and good, but they are rather disconnected from each other and in many cases do not provide very good facilities for distributing work among developers. If we want to drive these reports consistently to zero, some time spent on infrastructure would be worthwhile. What can we do to improve matters?

Release Note

This is not a user-visible specification.

Current state

We have lots of tools for tracking problems in the development release. Many have difficult to parse output:


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

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.

Reports should be better connected to each other, live in (or be linked to from) one place, be easily perusable (currently dormant?) the new version though maybe not as useful

Might be better to have a consolidated report listing packages with problems, rather than having to work through multiple reports
 * extend to release critical stuff?  currently targeted at bitesize stuff.
  * e.g. current version of NBS data, build failures on test rebuilds etc.
  * fix editing (adding comments?)
 * per package
 * can mark opportunities as irrelevant right now - want to keep generally static,  needs to be styled a bit.
 * merge with ? - stale?

Automatic upgrade testing
 * QA is taking over mvo's automatic upgrade testing
 * repurpose antimony (after CD building moves to new machine) as lintian(?) and piuparts runner

By comparison:

Lintian instance - useful to keep unpacked?  consider doing so?


PlusOneMaintenanceTeam/Specs/Infrastructure (last edited 2014-07-01 13:31:40 by cjwatson)