I'm agree with Dmitry. We can change version text. Use '2014.2-6.0-pre' in
openstack.yaml and '6.0-pre' in PRODUCT_VERSION. Yep, we need to test it
first. Also think about sorting on ui and other places where we can compare
versions.

On Mon, Oct 20, 2014 at 2:36 PM, Aleksandra Fedorova <afedor...@mirantis.com
> wrote:

> Hi, everyone,
>
> NOTE: I am moving this discussion into openstack-dev@ as we plan to
> deprecate fuel-...@lists.launchpad.net mailing list.
>
> Regarding the problem discussed:
>
> could you please add a bit more details about this versioning and how
> should it fit into our build process.
>
> Let's say we have 6.0 iso image. We build it now based on the
> PRODUCT_VERSION parameter from config.mk. How should we create the
> Technical Preview or GA iso images?
>
> Should we build them from scratch in a separate tasks with different set
> of predefined variables or should we choose one of the iso images we have
> and label it as Technical Preview and imprint this tag into iso somehow?
>
>
> On Mon, Oct 20, 2014 at 1:00 PM, Aleksey Kasatkin <akasat...@mirantis.com>
> wrote:
>
>> But we need to distinguish what Fuel was used to deploy this env. Aren't
>> we? E.g. install 5.1.1 env with Fuel 6.0 beta.
>> I'd propose to have both then (in version.yaml and in releases).
>>
>>
>> Aleksey Kasatkin
>>
>>
>> On Mon, Oct 20, 2014 at 11:55 AM, Alexander Kislitsky <
>> akislit...@mirantis.com> wrote:
>>
>>> Adding tag into the version will be the best solution - because we have
>>> it already implemented :-)
>>>
>>> On Mon, Oct 20, 2014 at 12:44 PM, Dmitriy Shulyak <dshul...@mirantis.com
>>> > wrote:
>>>
>>>> Maybe we dont need any separate entity to store this difference?
>>>> What if we can introduce tag of release into release version itself, so
>>>> it will look like:
>>>> 2014.2.1-6.0-beta or 2014.2.1-6.0.beta
>>>> and change name of the release accordingly - Ubuntu 6.0 Technical
>>>> Preview (beta)
>>>>
>>>> Is this an option?
>>>>
>>>> On Mon, Oct 20, 2014 at 11:28 AM, Aleksey Kasatkin <
>>>> akasat...@mirantis.com> wrote:
>>>>
>>>>> AFAIC, it is more like "release_stage" or just "stage" (see
>>>>> http://en.wikipedia.org/wiki/Software_release_life_cycle).
>>>>>
>>>>> Meaning of "release_name" is may be more like "Icehouse", "Juno" in
>>>>> OpenStack.
>>>>> I'm agree to store it in verslion.yaml.
>>>>>
>>>>>
>>>>> Aleksey Kasatkin
>>>>>
>>>>>
>>>>> On Mon, Oct 20, 2014 at 11:19 AM, Mike Scherbakov <
>>>>> mscherba...@mirantis.com> wrote:
>>>>>
>>>>>> Any progress on this?
>>>>>> I support this idea in general. Alex - may be you can prepare POC for
>>>>>> this and then we will present it to the crowd?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> On Wed, Oct 15, 2014 at 11:46 AM, Alexander Kislitsky <
>>>>>> akislit...@mirantis.com> wrote:
>>>>>>
>>>>>>> Hi, all!
>>>>>>>
>>>>>>> For Fuel release 6.0 we are going to have two versions: Technical
>>>>>>> Preview and GA.
>>>>>>> We need to consider these differences, for example in the statistics
>>>>>>> reports. So we need to store information about 'name of Fuel release'. I
>>>>>>> propose store this detailed information in the VERSION section of the
>>>>>>> verslion.yaml file with release info, placed in /etc/fuel/releases/. The
>>>>>>> field name can be 'release_name'.
>>>>>>>
>>>>>>> --
>>>>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>>>>> Post to     : fuel-...@lists.launchpad.net
>>>>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Mike Scherbakov
>>>>>> #mihgen
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>>>> Post to     : fuel-...@lists.launchpad.net
>>>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>>> Post to     : fuel-...@lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-...@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Aleksandra Fedorova
> bookwar
>
> --
> You received this message because you are subscribed to the Google Groups
> "fuel-core-team" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to fuel-core-team+unsubscr...@mirantis.com.
> For more options, visit https://groups.google.com/a/mirantis.com/d/optout.
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to