This is an overview of the ideal development workflow for the Mira Core Development Team. If you are a member of the Core team, or are an external contributor, please do try to follow this procedure so that your contributions may be merged into our development branch, trunk, as swiftly as possible.

1. You should create a separate branch for each individual task (be it a feature or bug fix) that you work on.
   • You should publish your personal branch to the mira namespace on Launchpad, to ensure that it automatically appears on Code : Mira Groupware
   • You should give your branch a unique name that represents the task for which it is needed
   • If you are a member of the Core team, it is preferable to publish a Team branch for ~mira-dev
     • Your branch would take the format: lp:~mira-dev/mira/uniqueBranchName
   • If you are not a member of the Core team, use your ~userName
     • Your branch would take the format: lp:~userName/mira/uniqueBranchName
2. You should make frequent commits in order to keep a detailed record of the changes made to your branch.
3. You should push those changes to Launchpad as frequently as you can.
4. Once you have completed the task and have tested it locally with success, propose to merge your branch into trunk. This will set off a process of review by the other members of the Core team, with an automatic email to the development mailing list.
5. Once your branch has been reviewed, if the code is deemed to be stable and you have successfully completed the task, your branch will be merged into trunk.

It would be helpful to look at the Useful Bazaar Techniques for Developers to learn some of the more detailed procedures that the Core developers use within this workflow.