+1 maintenance beyond April
The proposal for rolling releases is predicated on the belief that we will continue to maintain daily quality in the Ubuntu development release and that updates will continue to flow smoothly into the development pocket. This means we need to make sure we continue to provide adequate support for the +1 maintenance team.
Blueprint information
- Status:
- Not started
- Approver:
- Pete Graner
- Priority:
- Undefined
- Drafter:
- Steve Langasek
- Direction:
- Needs approval
- Assignee:
- Steve Langasek
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
-
ubuntu-13.04-month-5
- Started by
- Completed by
Whiteboard
[xnox] Can we please fix d-i vs kernel mismatches once and for all?! =) such that one doesn't get copied by britney out of -proposed without the other.
[adconrad] Your wish is granted, that's been fixed for months. (The bug is that overrides don't persist on migration, and the kernels get dumped to universe).
== Session Notes ==
WReview Team priorities
How are the priorities going to change based on a rolling release
Make sure both monthly snapshot and rolling release remain useful
more maintenance needed when the Debian freeze ends
https:/
http://
Q: Would it make sense to increase the size of the team from 1-2 to 3-4 given we are requiring more from daily quality going forward and we have been working against a nice slow debian cycle, which will not continue past the next debian release??
+1 Team could stand to have some more active coordination
current backlog is rather large apparently? http://
can haskell-* transitions be done in a non-virt ppa? or something like that, to prevent spamming update_excuses. - I think we should rather format that page so that it is easier to read/process (e. g. a dependency tree); blocking that set from autosyncs just to manually finish the transitions in a PPA doesn't appear to me to save any work?
= schedule constraints =
* Debian will likely release between now and May; this means there will be more +1 maintenance load by May
* have three people on the schedule for May
= volunteers =
cjwatson as usual
presumably adconrad
arges for a partial month (except April/May) - mgr approved
mathieu-tl (subject to manager approval)
laney (ditto)
jamespage
pitti for a 3/5 time (any month except May (sprint) or September (plumber's)
barry
stgraber
xnox
allison (May or later)
Work Items
Work items for ubuntu-
[adconrad] enable proposed-migration for multiple suites, starting with <stable>-proposed to <stable>-updates: TODO
[cjwatson] implement support in proposed-migration for removals: TODO
[pgraner] Figure out how to make sure people who are assigned to +1 maintenance are on the ball when their month starts: INPROGRESS
[pgraner] Put together the schedule for May/June with manager approval: INPROGRESS
[cjwatson] Fix the issue with pocket copies from -proposed losing the overrides and causing image build failures: DONE
