Open Stack

+1.

On Fri, Feb 13, 2015 at 11:41 AM, Sebastian Kalinowski
<skalinowski at mirantis.com> wrote:
> +1 for the whole idea, I really waited for it until first release of
> fuel-plugin-builder.
>
> Without tags it's hard to say which commit is included in PyPI release.
> Also automation of release process is a really nice thing and make it more
> transparent.
>
> 2015-02-13 9:59 GMT+01:00 Evgeniy L <eli at mirantis.com>:
>>
>> Hi,
>>
>> Since fuel plugins are going to be moved [1] from fuel-plugins repository
>> [2],
>> the only project which will be there is fuel plugin builder and plugins
>> examples
>> which are related to fuel plugin builder testing.
>>
>> Currently fuel plugin builder has its own release cycle, but we don't have
>> tags
>> for these versions, the suggestion is after plugins are removed from the
>> repository,
>> we should push tags for previous fpb releases.
>>
>> Tags can help with another problem, currently I manually publish new
>> version
>> on pypi, we can automatically build and publish new version after tag is
>> pushed.
>>
>> What do you think about that?
>>
>> Thanks,
>>
>> [1] https://review.openstack.org/#/c/151143/
>> [2] https://github.com/stackforge/fuel-plugins
>> [3]
>> https://github.com/stackforge/fuel-plugins/blob/master/fuel_plugin_builder/CHANGELOG.md
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>