+1 maintenance for Raring

Registered by Steve Langasek on 2012-10-29

Discuss how +1 maintenance will work in Raring: staffing, priorities

Blueprint information

Status:
Not started
Approver:
Steve Langasek
Priority:
High
Drafter:
Colin Watson
Direction:
Approved
Assignee:
Colin Watson
Definition:
Approved
Series goal:
Accepted for raring
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

- New responsibilities: keeping -proposed unclogged?
- talk to MOTU about getting involved?
- More aggressive removal of sources based on having had no binaries published for more than one cycle?
- List of links: https://wiki.ubuntu.com/PlusOneMaintenanceTeam/Specs/Priorities
- Previous schedule: https://wiki.ubuntu.com/PlusOneMaintenanceTeam#Schedule

Schedule:
[December]
Adam Conrad
Andy Whitcroft
Tim Gardner

[January]
Adam Conrad
Chris Arges
Micah Gersten

[February]
Adam Conrad
Matthias Klose
Michael Still

[March]
Adam Conrad
Colin Watson

[April]
Adam Conrad
Robie Basak

(?)

Work Items

Work items:
[vorlon] follow up with jasoncwarner about whether desktop can contribute this cycle (not needed): POSTPONED
[vorlon] follow up with popey about whether PS can contribute this cycle (not needed): POSTPONED
[adconrad] drive the scheduling of the +1 rotators: DONE
[adconrad] sort out clever ways to improve messaging about +1/MOTU engagement: INPROGRESS
[dholbach] work with Adam on efforts to involve/include MOTU: INPROGRESS
[cjwatson] do something about britney's obsolete sources mode: POSTPONED
[cjwatson] alert system for archive admins when NEW queue is deep/old: POSTPONED