On Wed, Oct 7, 2015 at 2:32 PM, Nir Soffer <[email protected]> wrote:
> This is also an issue when installing master for testing. > > I'm kind of tired of using "yum reinstall" or "yum downgrade" to install > latest code from master replacing 3.6 install, because master version is > sometimes older then 3.6 builds. > > How about having 4.x.99 on master - meaning the development version, never > change this version. > +1 for 4.17.99 on master. > > 4.x buids will be numbered 4.x.0-98 - always older then master. > > Or - use odd version for master, even versions for releases: > > 4.18.x - next stable versions > 4.19.x - next dev versions > 4.20.x - next stable versions > This is ok for me too. > ... > > Nir > > > On Wed, Oct 7, 2015 at 3:23 PM, Sandro Bonazzola <[email protected]> > wrote: > >> Hi, >> I already asked 4 times in the last 4 weeks, please bump vdsm version on >> master to something higher than what we have in 3.6 branch. >> ovirt-hosted-engine-setup is requiring vdsm >= 4.17.8 which is satisfied >> in 3.6 branch and not on master, being master on 4.17.2. >> If no action will be taken, on Monday I'll pull VDSM from 3.6 to master >> snapshot to satisfy dependencies, meaning vdsm from master won't ever be >> installed on nightly master. >> >> Thanks, >> -- >> Sandro Bonazzola >> Better technology. Faster innovation. Powered by community collaboration. >> See how it works at redhat.com >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/devel >> > > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
