Hi all, In response to a question regarding the normal workflow for developers, I am sorry that this has not been addressed more explicitly on the wiki; this is something I will have to add into the 'Instructions for Developers'.
It is, however, implicit in the 'Useful Bazaar Techniques for Developers', which is definitely worth a read-through (top to bottom, because some references are made to previous sections as it gets more advanced): http://miragroupware.org/wiki/doku.php/development/bazaartechniques Our Core team prefers to work on each individual task in a separate branch. So if, for example, one of us is working on a particular GUI feature (such as highlighting in the Contacts widget), or is restructuring the login system, a personal branch will be split from trunk in which that task will be developed. The advantage of this is that you can make frequent commits to keep a detailed record of the changes, and push those changes to Launchpad to your heart's content, and it will not affect the stability of trunk because it will be in an entirely separate branch. Then, when the task has been completed, the code is tested, reviewed by an appointed member of the Core team (often Alan) and, following this, the personal branch is merged into trunk. You will find examples of this on Mira's Code site on Launchpad: https://code.launchpad.net/mira On that page, all of the development branches below lp:mira (trunk) are personal branches created for individual features or tasks. I hope that clarifies it, somewhat! The Bazaar Techniques page should be able to fill in any gaps. :) Regards, Max Bossino Project Manager http://miragroupware.org ------------------------------------------------------------------------------ _______________________________________________ Mira-development mailing list Mira-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mira-development
