Patch Review Process Review

Registered by Daniel Holbach on 2010-03-30

Patch Review Process Review

Blueprint information

Status:
Complete
Approver:
Jono Bacon
Priority:
High
Drafter:
Daniel Holbach
Direction:
Approved
Assignee:
Daniel Holbach
Definition:
Approved
Series goal:
Accepted for maverick
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-10.10
Started by
Daniel Holbach on 2010-06-08
Completed by
Daniel Holbach on 2010-11-01

Related branches

Sprints

Whiteboard

Work items:
[nigelbabu] add more documentation to make the decision if it needs to go upstream or to debian easier (add examples): DONE
[bobbo] add more documentation to make the decision if it needs to go upstream or to debian easier (add examples): DONE
[dholbach] add more documentation to make the decision if it needs to go upstream or to debian easier (add examples): DONE
[nigelbabu] clarify to keep the team subscribed (or unsubscribe team and untag patch; on the next patch upload, the script will add the team again): DONE
[brian-murray] Brian to keep stats to bugs on patch tag - speak nigelbabu: DONE
[brian-murray] Brian to publish bzr branch where script it is in ubuntu-qa-tools: DONE
[dholbach] Nigel to document "black listing process": DONE
[bobbo] add documentation about how to turn a patch into a merge proposal if it's a project maintained in Launchpad: DONE
[dholbach] add documentation about how to get it included in the sponsors queue: DONE
[bdrung] sponsor-patch: script that applies the patch and uploads it to a PPA: DONE
[bobbo] add feature to edit-patch that directly applies a given patch (bug 586787): DONE
[stefanlsd] speak with jml re merge proposals for patches (merge conflict - error - push output to ppa) - sending upstream - need well defined spec on this & udd (Spoke with jml. This is not done LP side yet. Should be mostly possible client side and using LP API): DONE
[persia] Emmet to clarify buckets and TODO lists!: TODO

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.