Infrastructure improvements for development release maintenance
We have many reports that help us keep track of automatically-
Blueprint information
- Status:
- Started
- Approver:
- Steve Langasek
- Priority:
- Medium
- Drafter:
- Colin Watson
- Direction:
- Approved
- Assignee:
- Colin Watson
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Colin Watson
- Completed by
Whiteboard
Work items:
[broder] Set up lintian lab: DONE
[cjwatson] Set up piuparts: TODO
Generate separate report from lintian of Ubuntu-specific packages: TODO
Generate JSON output from lintian for harvest: TODO
[cjwatson] Generate JSON output from piuparts for harvest: TODO
[cjwatson] Move generation of *-mismatches reports off ftpmaster into ubuntu-
[cjwatson] HTMLify *-mismatches reports: DONE
Implement annotations and bug links in *-mismatches reports (if Harvest is not enough): TODO
HTMLify conflict checker output: TODO
Implement annotations and bug links in conflict checker output (if Harvest is not enough): TODO
[laney] Merge transition tracker from Debian trunk: DONE
[laney] Add transition index: DONE
[cjwatson] Fix transition tracker runner to remove stale output: TODO
Prepare and advertise suitable +1 maintenance overview URL in Harvest: TODO
[broder] extend lintian to report on packages using dpkg-maintscrip
2011-11-18 cjwatson: I've dropped the work item to take over and update the weather report, because as explained in the wiki page it seems unlikely that it will be able to simultaneously meet the needs of release management and the +1 maintenance team. I would rather limit the scope and have us do a good job on the latter.
Work Items
Dependency tree

* Blueprints in grey have been implemented.