Re: [openstack-dev] [Fuel] Different versions for different components

2015-12-16 Thread Bartłomiej Piotrowski 
On 2015-12-15 18:16, Roman Prykhodchenko wrote:
> Aleksandra,
> 
> thank you for the clarification, it makes sense to me now.
> 
> In my opinion our current approach is not flexible at all and very outdated.

After splitting fuel-web to smaller components we realized that some of
them may be actually used outside of a master node as standalone things.

In this case it is required for some of them to be distributable and
upgradable over PyPi. It’s also required for different components to be
able to make

 minor releases to release important bug fixes and improvements for
users that use them outside their master nodes. For that we should be
able to modify the minor version independently.
> 
> Do you think it is possible to achieve in the observable future.


Roman,

there are tens of different workflows related to managing version during
development cycle. It's hard to call any of these "outdated". Bumping
the release number right after branching (and/or tagging) stable one is
pretty common and I don't see what is actually wrong with it.

I think Alexandra clearly described how our workflow looks like. It
doesn't limit making minor releases or pushing these to PyPI. Is there
some reason that makes it impossible to push fuelclient 7.* to Debian
repositories? You didn't describe anything specific in last two messages.

Bartłomiej

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Different versions for different components

2015-12-15 Thread Roman Prykhodchenko 
Aleksandra,

thank you for the clarification, it makes sense to me now.

In my opinion our current approach is not flexible at all and very outdated. 
After splitting fuel-web to smaller components we realized that some of them 
may be actually used outside of a master node as standalone things. In this 
case it is required for some of them to be distributable and upgradable over 
PyPi. It’s also required for different components to be able to make minor 
releases to release important bug fixes and improvements for users that use 
them outside their master nodes. For that we should be able to modify the minor 
version independently.

Do you think it is possible to achieve in the observable future.


- romcheg

> 15 груд. 2015 р. о 12:21 Aleksandra Fedorova  
> написав(ла):
> 
> Roman,
> 
> we use 8.0 version everywhere in Fuel code _before_ 8.0 release. We
> don't use bump&tag approach, rather bump version, run a development
> and test cycle, then create release and tag it.
> 
> In more details:
> 
> 1) there is a master branch, in which development for upcoming release
> (currently 8.0) happens. All hardcoded version parameters in master
> branch are set to 8.0.
> 
> 2) at Soft Code Freeze (which is one week from now) we create
> stable/8.0 branch from current master. Then we immediately bump
> versions in master branches of all Fuel projects to 9.0.
> Since SCF we have stable/8.0 branch with 8.0 version and master with
> 9.0, but there is still bugfixing in progress, so there might be
> changes in stable/8.0 code.
> 
> 3) On RTM day we finally create 8.0 tags on stable/8.0 branch, and
> this is the time when we should release packages to PyPI and other
> resources.
> 
> 
> 
> On Tue, Dec 15, 2015 at 2:03 PM, Roman Prykhodchenko  wrote:
>> Folks,
>> 
>> I can see that version for python-fuelclient package is already [1] set to
>> 8.0.0. However, there’s still no corresponding tag and so the version was
>> not released to PyPi.
>> The question is it finally safe to tag different versions for different
>> components? As for Fuel client we need to tag 8.0.0 to push a Debian package
>> for it.
>> 
>> 
>> 1. https://github.com/openstack/python-fuelclient/blob/master/setup.cfg#L3
>> 
>> 
>> - romcheg
>> 
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
> 
> 
> 
> --
> Aleksandra Fedorova
> Fuel CI Team Lead
> bookwar
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Different versions for different components

2015-12-15 Thread Aleksandra Fedorova 
Roman,

we use 8.0 version everywhere in Fuel code _before_ 8.0 release. We
don't use bump&tag approach, rather bump version, run a development
and test cycle, then create release and tag it.

In more details:

1) there is a master branch, in which development for upcoming release
(currently 8.0) happens. All hardcoded version parameters in master
branch are set to 8.0.

2) at Soft Code Freeze (which is one week from now) we create
stable/8.0 branch from current master. Then we immediately bump
versions in master branches of all Fuel projects to 9.0.
Since SCF we have stable/8.0 branch with 8.0 version and master with
9.0, but there is still bugfixing in progress, so there might be
changes in stable/8.0 code.

3) On RTM day we finally create 8.0 tags on stable/8.0 branch, and
this is the time when we should release packages to PyPI and other
resources.



On Tue, Dec 15, 2015 at 2:03 PM, Roman Prykhodchenko  wrote:
> Folks,
>
> I can see that version for python-fuelclient package is already [1] set to
> 8.0.0. However, there’s still no corresponding tag and so the version was
> not released to PyPi.
> The question is it finally safe to tag different versions for different
> components? As for Fuel client we need to tag 8.0.0 to push a Debian package
> for it.
>
>
> 1. https://github.com/openstack/python-fuelclient/blob/master/setup.cfg#L3
>
>
> - romcheg
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Aleksandra Fedorova
Fuel CI Team Lead
bookwar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Different versions for different components

2015-12-15 Thread Roman Prykhodchenko 
Folks,

I can see that version for python-fuelclient package is already [1] set to 
8.0.0. However, there’s still no corresponding tag and so the version was not 
released to PyPi.
The question is it finally safe to tag different versions for different 
components? As for Fuel client we need to tag 8.0.0 to push a Debian package 
for it.


1. https://github.com/openstack/python-fuelclient/blob/master/setup.cfg#L3 



- romcheg



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev