openerp-community team mailing list archive

[Stefan Rijnhart <stefan@xxxxxxxx>]

Hi Joël,

Maybe I don't understand, but having one addon per repo does that mean
that when an API change requires a change in all the banking addons (for
instance), that I have to make a pull request for all those repos?

I'd be in favour of keeping OCA projects in bzr for 7.0 and in GitHub
for 8.0. Should be less work for everybody. Just because OpenERP SA
causes this overnight disruptive change does not mean that the OCA has
to follow. Or does the app store not support Launchpad anymore either?

Cheers,
Stefan.



On 16-05-14 17:16, Joël Grand-Guillaume wrote:
> Dear community,
>
>
> After the announcement of the brand new odoo instead of OpenERP, the
> main changes for contributors currently is the switch to Github. As I
> know, most of you waited for such a move ! Now it's done :) Though it
> remain a quite huge question : How the hell do we, as the community,
> will manage this switch ?
>
> I know there is lots of side questions (like making one repository per
> module, using subtree and many more). I see those options:
>
> a) Move all projects from LP to Github, but only the 7.0 series to
> create only the master branch. Every devs should create the pull
> request needed if they want their LP MP to be shown as pull request on
> github. Then for serie 8.0, we start with one repo by module (as in
> option c):
>
> + => one LP project = one github project, Easy, quick,simple to
> understand, only "still active" MP will be ported by each devs
> - => Every devs will have to rebuild the pull request, loss of review
> infos in the pull request (though people can copy/paste the link to LP)
>
>
> b) Move all projects from LP to Github and try to take all branches
> related to a project using [1], create the master branch from the 7.0
> series. Then all devs will have to take back his branch, branch by
> branch, in his own name (that process [1] was use to move openstack to
> github). Then for serie 8.0, we start with one repo by module (as in
> option c):
>
> + => one LP project = one github project, Keep all branches of all
> projects
> - => Doesn't help to take back the MP as pull request, will let lots
> of "obsolete" branches
>
>
> c) Try to immediately split repository to have one repo by module, all
> owned by the OCA project (only one project, many, many repos). Just
> making one repo by module. Then we can have those many repos grouped
> by topic using submodule (here an example:
> https://github.com/camptocamp/puppet-modules). By topic I mean "Apps"
> (like sale, purchase, ..).
>
> + => We have one repo by module and start "clean" on github
> - => Not that easy to split, not clear exactly how to do that, we have
> the risk that by the time we figure that out we remain on LP for quite
> a while, change the architecture and tools all at once.
>
>
> My suggestion to allow a fast move forward is option a) as the following:
>
> 1) Take all OCA projects on LP and create one under the OCA umbrella
> on github
> 2) Then I suggest to create the master branch on Github from the 7.0
> series on LP. Older one remain on LP only.
> 3) All current MPs must be made as pull request by his owner on GitHub
> to be merged.
> 4) All the 7.0 series starts on Github as soon as we have build them
> all (should not take more than 1 or 2 days to achieve. The older one
> (5, 6, 6.1) remain on LP.
> 5) For 8.0, we starts creating all needed sub-module repo
>
> Mains args:
>
>  * Easy and fast
>  * Make a "smooth" transition as projects are kept, "just" moved on github
>  * Avoid having old MP or obsolete branches in the OCA umbrella
>  * For 7.0 serie we have everything on github, so we avoid working
> with both git and bzr
>  * For older serie we keep all on bzr, while future v8.0 will have a
> clean one repo by module solution
>
>
> Who's in favor of which option here (a,b,c) ? Any others I missed ?
>
>
> Thanks for your vote ! Please try to be as short as possible on your
> answer, so we can see who's voting for which option :)
>
>
>
> Best regards,
>
>
>
> Joël
>
>
>
>
>
>
> [1] https://github.com/termie/lp2gh/blob/master/docs/moving_branches.rst
>
>
>
>
> -- 
>
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Joël Grand-Guillaume*
> Division Manager
> Business Solutions
>
> +41 21 619 10 28
> www.camptocamp.com <http://www.camptocamp.com/>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp


-- 
Therp - Maatwerk in open ontwikkeling

Stefan Rijnhart - Ontwerp en implementatie

mail: stefan@xxxxxxxx
tel: +31 (0) 614478606
http://therp.nl
https://twitter.com/therp_stefan