2014/1/8 Jean C <[email protected]> > Hi all, > > 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 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. > > 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. >
We're not really strictly following the workflow but we have set up a rietveld instance [1] for some of the developments we manage between Zikzakmedia and NaN·tic. The disadvantage we find with reviews is that they're not quick to manage when you have several developments. In some cases we use pull requests were each company has its own repositories but then there're several repositories (which we also try to avoid). We've developed a tool [1] that uses some configuration files [2] to fetch modules from several repository type, by now git and mercurial but we aim to support codereviews. Allows cloning them, pulling, running "status", etc. It does it in several threads which makes it quite fast. We also manage a patch queue using quilt. [1] http://codereview.tryton.org/ [2] https://bitbucket.org/nantic/tryton-utils [3] https://bitbucket.org/nantic/tryton-config -- Albert Cervera i Areny Tel. 93 553 18 03 @albertnan www.NaN-tic.com
