Hello, thanks for mentioning this. I’ve tagged python-muranoclient’s stable/juno branch with 0.5.5.1. I’ve noticed that most clients do not follow '*-eol' convention, it’s mostly present in non-client repos. Please take a look at current state of the branch and if everything’s ok — I believe it’s safe to remove stable/juno there.
-- Kirill Zaitsev Murano team Software Engineer Mirantis, Inc On 4 February 2016 at 04:10:26, Clark Boylan ([email protected]) wrote: On Thu, Jan 28, 2016, at 05:18 AM, Kirill Zaitsev wrote: > Hello, I’d like to request deletion of stable/juno branch from murano, > murano-dashboard, murano-agent and python-muranoclient repositories. As > far as I know — I do not have branch deletion permissions myself. > > As far as I see, those branches have been tagged with EOL 2014.2.4 tag > (0.5.5 for client), so there are no unreleased changes there. We also do > not have any commits on the review for stable/juno, so we no longer need > those branches. > > We also have discussed this > http://eavesdrop.openstack.org/meetings/murano/2016/murano.2016-01-26-17.00.log.html > > in IRC meetings. > I have removed stable/juno from murano, murano-dashboard, and murano-agent. I did not remove it from python-muranoclient because there is no tag on the tip of stable/juno. Generally we tag the tips of these branches something like 'juno-eol' as well just to be extra clear which you may consider for the client and the other projects. Let us know when you have properly tagged the tip of the stable/juno branch on python-muranoclient and we can remove that branch as well. Clark
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
