Re: [ovirt-devel] [VDSM] New versioning scheme

adding infra also, in case we need to do changes in ci/builds. On Wed, Jun 1, 2016 at 1:58 PM, Francesco Romani <fromani(a)redhat.com&gt; wrote: > ----- Original Message ----- > > From: "Nir Soffer" <nsoffer(a)redhat.com&gt; > > To: "devel" <devel(a)ovirt.org&gt;, "Dan Kenigsberg" <danken(a)redhat.com&gt;, > "Francesco Romani" <fromani(a)redhat.com&gt;, "Piotr > > Kliczewski" <pkliczew(a)redhat.com&gt;, "Adam Litke" <alitke(a)redhat.com&gt;, > "Yaniv Bronheim" <ybronhei(a)redhat.com&gt;, "Sandro > > Bonazzola" <sbonazzo(a)redhat.com&gt; > > Sent: Wednesday, June 1, 2016 12:51:49 PM > > Subject: [VDSM] New versioning scheme > > > > Hi all, > > > > We are going to branch 4.0 today, and it is a good time to update our > > versioning scheme. > > > > I suggest to use the standard ovirt versioning, use by most projects: > > > > 1. master > > > > vdsm-4.19.0-201606011345.gitxxxyyy > > > > 2. 4.0 > > > > vdsm-4.18.1 > > > > The important invariant is that any build from master is considered > newer > > compare with the stable builds, since master always contain all stable > > code, and new code. > > > > Second invariant, the most recent build from master is always newer > compared > > with any other master build - the timestamp enforces this. > > > > Thoughts? > > +1 > > given how Vdsm build system works, it should be a matter of just pushing > the 4.19.0 tag against master after the branch > >

Bests, > > -- > Francesco Romani > RedHat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > > > -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)