Unblocking Developers
A lot of our development processes involve a review or approval step. Let's review how we've done in the P release and see what we can improve for Q.
Blueprint information
- Status:
- Not started
- Approver:
- Jono Bacon
- Priority:
- Undefined
- Drafter:
- Daniel Holbach
- Direction:
- Approved
- Assignee:
- Daniel Holbach
- Definition:
- Approved
- Series goal:
- Accepted for quantal
- Implementation:
-
Unknown
- Milestone target:
-
ubuntu-12.10
- Started by
- Completed by
Whiteboard
Bottleneck Status: http://
- Sponsoring
- http://
- Archive admin tasks
AA team may be growing?
AA team itself not overworked; AAs do other things
Removing syncs, backports big improvements
NEW review? Seems to be mostly under control
- Backports
- Removing the AA requirement
- broder working on backporter bot for testing
(http://
- Docs are better (https:/
- Backport has annoying testing requirements
- Can we relax requirements for a backport to multiple releases?
- SRU
SRU process discussed separately (not really any conclusions, but want it to move faster)
Work Items
Work items for quantal-alpha-2:
[dholbach] refer to backports/sru/etc. processes in packaging guide (bug 1017984): DONE
[dholbach] check docs to see what we recommend to keep the sponsoring queue clean: DONE
[dholbach] mail/blog about techniques to keep the queue clean: DONE
[dholbach] socialise the idea of patch piloting across non-Canonical people (hit-list: broder, ...): DONE
Work items:
[stefanor] : Have requestbackport explain that it's not for bugs: DONE
[laney] Follow up on discussion to relax testing requirements for backports :(: POSTPONED
[broder] talk to pitti and find out how he works his sponsoring magic: TODO
[andrewsomething] Go through and look for MOTUs that should be core-devs: TODO
