On Jan 8, 2014, at 2:04 PM, Jean C <[email protected]> wrote:
> We are in the process of improving our internal development workflow, and > would like to know your experiences and how you are currently working. We have been asked this question several times and I decided to blog about the development workflow we use at Openlabs [1]. By the time I wrote it, the blog had become really huge, so it is now split into 5 parts ;-) > > We are currently using mercurial with bitbucket. We want to try on the > pull-request workflow, but we understood it may be difficult regarding the > way mercurial manages branches. Git is far better at handling branches (than mercurial) and github makes it even better. I have explained how we manage the repositories when we maintain modules for multiple major versions of Tryton. The workflow is a bit different for customer specific modules where we definitely have versions within the same series which have schema updates, but require a good way to manage development and stable production releases. > > Any idea / possibility (we will research what you may not have the time to > detail) is welcomed, we just want to have an idea of how the community is > working. Hope this helps and we look forward to your thoughts. [1] http://engineering.openlabs.co.in/post/72769621921/tryton-development-workflow-at-openlabs [2] http://engineering.openlabs.co.in/post/72769275514/part-1-tryton-development-workflow-series-repository Thanks & Regards Sharoon Thomas Openlabs Technologies & Consulting (P) Limited w: http://www.openlabs.co.in m: +1 813.793.6736 (OPEN) Extn. 200 t: @sharoonthomas - We win when our customers win
signature.asc
Description: Message signed with OpenPGP using GPGMail
