Development Workflow Review

Registered by Daniel Holbach on 2010-03-30

Find opportunities for reducing the complexity of the workflow as a developer. In the maverick cycle we will exclusively review the case where contributors attempt to fix a bug in an existing package.

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 maverick-alpha-2
Started by
Daniel Holbach on 2010-06-17
Completed by
Daniel Holbach on 2010-06-17

Related branches

Sprints

Whiteboard

Work items:
[dholbach] Review existing "How to fix a bug in Ubuntu" documentation: DONE
[dholbach] Document requirements: LP Account, ssh key: DONE
[dholbach] Update documentation to use Distributed Development: DONE
[dholbach] Factor in information about edit-patch and forwarding patches: DONE
[dholbach] Factor in information about our release cycle: DONE
[dholbach] Clarify expectations about getting it applied: DONE
[dholbach] Review "entry-points" for fixing a bug and update links (helping with bugs, launchpad, etc.): DONE
[dholbach] Conduct field test (ask semi technical people to "go and fix an ubuntu bug": DONE
[dholbach] Talk to Launchpad developers if they're interested in adding a "fix ubuntu bug" link in Malone (bug 588322): DONE

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.