2014/1/9 Mathias Behrle <[email protected]>: > * Jean C: " [tryton-dev] What is your internal workflow" (Wed, 8 Jan 2014 > 09:34:59 +0100): > >> 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. > > One of your primary decisions will be, if you want to maintain versions older > than current. If you want to do so with mercurial, the layout from tryton.org > seems still the way to go (while I have to admit, that it is looong ago, that > I > looked at the branching capabilities of mercurial). Publishing on the usual > hosters will be tedious. > If you don't intend to do maintenance of different versions, you can choose > the > same way as Zikzakmedia and NaN·tic and just publish the current branch.
Note that we created 3.0 branches for all repositories, and will add 3.2 when it is released, etc. > If you want to publish and work actively with different branches I think git > is > superior to mercurial (like the way openlabs published a Tryton mirror [1]). > > Internally at MBSolutions we are working with both, using mercurial for > development and maintenance (to minimze overhead when working with upstream), > but strictly git for Debian packaging [2]. > > For me it boils down to the main question, if you want to do series > maintenance. Then the next steps will be easier to evaluate. > > > [1] https://github.com/tryton > [2] > https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?a=project_list&s=tryton%2F&btnS=Search > > -- > > Mathias Behrle > MBSolutions > Gilgenmatten 10 A > D-79114 Freiburg > > Tel: +49(761)471023 > Fax: +49(761)4770816 > http://m9s.biz > UStIdNr: DE 142009020 > PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 -- Albert Cervera i Areny Tel. 93 553 18 03 @albertnan www.NaN-tic.com
