Contributors mailing list archives
Re: tagging OCB branchesby
David Arnold BA HSG / Analista
315 304 13 68/ firstname.lastname@example.org
devCO - empresa de consultoría de sistemas (en fundación)
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. devCO is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
Hello David, I don't really see the point in the 'weekly' tags: there is no promise of stability on the version you get on mondays, nothing which makes it "special". Alexandre On 28/10/2015 18:23, David Arnold wrote: > Alexandre: You probably have already taken into account: > > *Split tags into:* > > *For version 9.0:* > 9.0.weekly.YYYY-MM-DD > 9.0.daily.YYYY-MM-DD > > *For version 8.0:* > 8.0.weekly.YYYY-MM-DD > 8.0.daily.YYYY-MM-DD > > Adhering to such or a similar standard, we can easily and flexibly work > with those tags in a regular expression. Like only updating every month > or year. As weekly is a common cycle, It would help to encode it as well > as this is not easily retrieved from the date without mapping. > > Best Regards, > > David > > El mié., 28 oct. 2015 a las 11:08, Holger Brunn (<email@example.com > <mailto:firstname.lastname@example.org>>) escribió: > > > Yes I agree. I'll work on this next week (tagging + moving the merge process > > on an OCA server), unless someone steps in first. -- > > about the merge process: If we want to continue using the account oca-git-bot, > I'll have to add the public ssh key to this github account. > > Then just run https://github.com/OCA/maintainer-tools/blob/master/tools/ocb-sync.sh nightly and have it mail its output to everyone interested. Maybe use > a mail group for this on the OCA instance? > > In our setup, we also have a file ocb-sync.sh.conf with content > GITDIR="/home/oca-git-bot/git" > to have the repo live there and not in /tmp. > > Then whoever picks up a conflict should document it here: > https://github.com/OCA/OCB/wiki/Conflict-resolutions-OCB-synchronization > > We might also use the wiki as a mutex to avoid double work if nobody has a > better idea. > > Please tell me when it's up and running so that I can deactivate our cronjob. > > -- > Therp - Maatwerk in open ontwikkeling > > Holger Brunn - Ontwerp en implementatie > > mail: email@example.com <mailto:firstname.lastname@example.org> > web: http://therp.nl > > _______________________________________________ > Mailing-List: http://odoo-community.org/groups/contributors-15 > Post to: mailto:email@example.com > <mailto:firstname.lastname@example.org> > Unsubscribe: http://odoo-community.org/groups?unsubscribe > > _______________________________________________ > Mailing-List: http://odoo-community.org/groups/contributors-15 > Post to: mailto:email@example.com > Unsubscribe: http://odoo-community.org/groups?unsubscribe > -- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.com