Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Folks, I want to bring this up again. There were no progress since last Oleg's mail, and we must decide. It's good that we still have "2015.1.0-8.0" version while OpenStack uses "Liberty" name for versions. Let's decide which name to use, file a bug and finally resolve it. - Igor On Thu, Oct

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Hi folks, I would propose to keep current versioning schema until fuel release schedule is fully aligned with OpenStack releases. AFAIK it is expected to happen since 9.0. After it we can switch to OpenStack version names. BR, Dmitry. On Tue, Dec 15, 2015 at 8:41 PM, Igor Kalnitsky

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

I have a few changes in review [0] that implement a plan outlined in the bug [1] for seamless merge of the new versioning schema (liberty-8.0). With those changes merged in order, we should be OK without changing ISO in Fuel infra. I also have version of ISO with green BVT that incorporates

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Igor, it is interesting that you mention backward compatibility in this context. I can see lots of code in Nailgun that checks for release version to enable/disable features that were added or removed more than 2 releases before [1] [2] [3] (there's a lot more). What should we do about that

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Oleg, I think we can remove this function for new releases and keep them only for backward compatibility with previous ones. Why not? If there's a way to do things better let's do them better. :) On Sat, Oct 17, 2015 at 11:50 PM, Oleg Gelbukh wrote: > In short, because of

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

After closer look, the only viable option in closer term seems to be 'liberty-8.0' version. It does not to break comparisons that exist in the code and allows for smooth transition. -- Best regards, Oleg Gelbukh On Fri, Oct 16, 2015 at 5:35 PM, Igor Kalnitsky wrote: >

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Why can't we use 'liberty' without 8.0? On Sat, 17 Oct 2015 at 19:33, Oleg Gelbukh wrote: > After closer look, the only viable option in closer term seems to be > 'liberty-8.0' version. It does not to break comparisons that exist in the > code and allows for smooth

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

In short, because of this: https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/db/sqlalchemy/models/release.py#L74-L99 Unless we use dashed 2-component version where OpenStack version comes first, followed by version of Fuel, this will break creation of a cluster with given release.

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Hey Oleg, I've read the post [1] and I didn't get how exactly minor releases of *stable* branch will be versioned? Let's say 2015.2.0 is Liberty. How 2015.2.1 will be versioned? [1] http://ttx.re/new-versioning.html Thanks, Igor On Thu, Oct 15, 2015 at 6:59 PM, Oleg Gelbukh

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Igor, The point is that there's no 2015.2.0 version anywhere in OpenStack. So every component will be versioned separately, for example, in Libery, Nova has version 12.0.0, and minor release of it is going to have version 12.0.1, while Keystone, for instance, will have version 11.0.0 and 11.0.1

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Oleg, Yes, I know. Still you didn't answer my question - are they planning to release stable branches time-to-time? Like I said, Liberty is something similar 2015.2.0. How they will name release of something like 2015.2.1 (stable release, with bugfixes) ? Or they plan to drop it? Thanks, Igor

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Oleg, Awesome! That's what I was looking for. :) - Igor On Fri, Oct 16, 2015 at 5:09 PM, Oleg Gelbukh wrote: > Igor, > > Got your question now. Coordinated point (maintenance) releases are dropped. > [1] [2] > > [1]

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Igor, Got your question now. Coordinated point (maintenance) releases are dropped. [1] [2] [1] http://lists.openstack.org/pipermail/openstack-dev/2015-May/065144.html [2] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Fliberty_releases -- Best regards, Oleg Gelbukh On Fri,

[openstack-dev] [fuel] OpenStack versioning in Fuel

Hello, I would like to highlight a problem that we are now going to have in Fuel regarding versioning of OpenStack. As you know, with introduction of the Big Tent policy it was decided that since Liberty dev cycle versioning schema of the whole project changes. Year-based versions won't be