Hi guys, I have to say something about beta releases.

As far as I know our beta release has the same version
5.1 as our final release.

I think this versions should be different, because in case
of some problem it will be much easier to identify what
version we are trying to debug.

Also from the irc channel I've heard that somebody wanted
to upgrade his system to stable version, right now it's impossible
because upgrade system uses this version for names of
containers/images/temporary directories and we have
validation which prevents the user to run upgrade to the
same version.

In upgrade script we use python module [1] to compare versions
for validation.
Let me give an example how development versions can look like

    5.1a1 # alpha
    5.1b1 # beta 1
    5.1b1 # beta 2
    5.1b1 # beta 3
    5.1    # final release

[1]
http://epydoc.sourceforge.net/stdlib/distutils.version.StrictVersion-class.html

Thanks,


On Tue, Aug 26, 2014 at 11:15 AM, Mike Scherbakov <mscherba...@mirantis.com>
wrote:

> Igor,
> thanks a lot for improving UX over it - this table allows me to see which
> ISO passed verification tests.
>
>
> On Mon, Aug 25, 2014 at 7:54 PM, Vladimir Kuklin <vkuk...@mirantis.com>
> wrote:
>
>> I would also like to add that you can use our library called devops along
>> with system tests we use for QA and CI. These tests use libvirt and kvm so
>> that you can easily fire up an environment with specific configuration
>> (Centos/Ubuntu Nova/Neutron Ceph/Swift and so on). All the documentation
>> how to use this library is here:
>> http://docs.mirantis.com/fuel-dev/devops.html. If you find any bugs or
>> gaps in documentation, please feel free to file bugs to
>> https://launchpad.net/fuel.
>>
>>
>> On Mon, Aug 25, 2014 at 6:39 PM, Igor Shishkin <ishish...@mirantis.com>
>> wrote:
>>
>>> Hi all,
>>> along with building your own ISO following instructions [1], you can
>>> always download nightly build [2] and run it, by using virtualbox scripts
>>> [3], for example.
>>>
>>> For your conveniency, you can see a build status table on CI [4]. First
>>> tab now refers to pre-5.1 builds, and second - to master builds.
>>> BVT columns stands for Build Verification Test, which is essentially
>>> full HA deploy deployment test.
>>>
>>> Currently pre-5.1 and master builds are actually built from same master
>>> branch. As soon as we call for Hard Code Freeze, pre-5.1 builds will be
>>> reconfigured to use stable/5.1 branch.
>>>
>>> Thanks,
>>>
>>> [1]
>>> http://docs.mirantis.com/fuel-dev/develop/env.html#building-the-fuel-iso
>>> [2] https://wiki.openstack.org/wiki/Fuel#Nightly_builds
>>> [3] https://github.com/stackforge/fuel-main/tree/master/virtualbox
>>> [4] https://fuel-jenkins.mirantis.com/view/ISO/
>>> --
>>> Igor Shishkin
>>> DevOps
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Yours Faithfully,
>> Vladimir Kuklin,
>> Fuel Library Tech Lead,
>> Mirantis, Inc.
>> +7 (495) 640-49-04
>> +7 (926) 702-39-68
>> Skype kuklinvv
>> 45bk3, Vorontsovskaya Str.
>> Moscow, Russia,
>> www.mirantis.com <http://www.mirantis.ru/>
>> www.mirantis.ru
>> vkuk...@mirantis.com
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Mike Scherbakov
> #mihgen
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to