----- Original Message ----- > From: "Nir Soffer" <[email protected]> > To: "devel" <[email protected]>, "Dan Kenigsberg" <[email protected]>, > "Francesco Romani" <[email protected]>, "Piotr > Kliczewski" <[email protected]>, "Adam Litke" <[email protected]>, "Yaniv > Bronheim" <[email protected]>, "Sandro > Bonazzola" <[email protected]> > 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 [email protected] http://lists.ovirt.org/mailman/listinfo/devel
