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
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.
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
Roman,
we use 8.0 version everywhere in Fuel code _before_ 8.0 release. We
don't use bump 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)
