← Back to team overview

ocb team mailing list archive

OCB, recovering from the VCS move

 

Hi,

at this point, the GitHub repo is now leading for the stable OpenERP
release 7.0 ([1]). The old Launchpad projects server, addons and web
have been combined into this single GitHub repo, which the addons and
web/addons put into a new addons directory in the repo root dir (not in
openerp/addons). The old bzr rev ids have been preserved ([2]) in the
migrated repo.

This makes the whole OCB-replay setup obsolete overnight and poses us
for the following problems:

1) We need a new process to adopt changes in upstream to OCB. For 8.0
this should be easy using git rebase if I understand correctly (which I
may not) but for 7.0 we would need to push lp:ocb/7.0 to OCB in the same
combined layout, and be able to identify commits that are in odoo/7.0
but not in GitHub OCB/7.0. Does anyone know if this is at all possible?
Are there alternative solutions?

2) My idea of migrating changes in OCB/7.0 to OCB/8.0 was also based on
this replay. It would be nice to know if the solution to (1) could be
extended to facilitate this as well.

3) Existing proposals on OCB/7.0 still need to be dealt with. Should
they be resubmitted on GitHub as pull requests manually, referring to
the LP issue? 6.1 is hardly maintained by OpenERP SA anymore and can
stay on Launchpad IMHO.

4) We need to figure out, document and instruct the contributors how to
contribute to OCB on GitHub. On Launchpad, it was quite easy to see what
the status was of an issue in each project (even if it was a pain to
administer and working with separate projects). I'd like to keep that
kind of information for new issues and patches on the new platform.

As you have gathered by now, I was not a git user before this and I have
very little to bring to this conversation. Please help ;-)

On the side, I am actually quite angry about this zeroday change of
workflow. We all missed the webinar due to sound not working on WebEx on
64-bit Linux systems, but I saw the slide and it said 'GitHub for trunk
only'. Today I find out by asking Olivier on Twitter that the 'stable'
version of OpenERP has also moving to the new VCS, with its new combined
file layout, without any coordination with the community. But never mind
that , the practical side of restarting OCB is actually more important
to me.

Cheers,
Stefan.

[1] https://twitter.com/odony/status/467313187365584896
[2] For example:
https://github.com/odoo/odoo/commit/37c41f9c78ef7ef2eab0f1cd74f907cbe824c95c

-- 
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



Follow ups