Contributors mailing list archives
Re: tagging OCB branchesby
Camptocamp France SAS, Alexandre Fayolle
The main problem is that you can't fetch a SHA1. When freezing the OCB version with the buildout recipe using a sha1, relaunching bin/buildout means fetching all the new changesets from github and then performing a checkout of the changeset with the SHA1, which is less efficient than fetching a tag (esp. when you are already on the desired changeset).
2015-10-26 15:23 GMT+01:00 Lorenzo Battistini <email@example.com>:
On 26 October 2015 at 14:37, Alexandre Fayolle <firstname.lastname@example.org> wrote:During the Pycon fr sprint, I've discussed with Georges about the use of the anybox recipe, and I think a good thing we could do in the OCB branches is to add a git tag on each branch after the daily merge of the upstream branch (tag such as 8.0-20151026). This would ease the work of those who wish to freeze the version of odoo for a project, by letting them use this tag, rather than using a sha1 (or maintaining a mirror of OCB and maintaining tags on that mirror).Assuming that SHA1 of commits of stable branches will not change/disappear, what problem do you see with using them to freeze instances?