[openstack-dev] [rally][dragonflow][ec2-api][PowerVMStackers][murano] Tagging rights
Doug Hellmann
doug at doughellmann.com
Mon Apr 23 22:31:17 UTC 2018
Excerpts from Andrey Pavlov's message of 2018-04-23 21:42:56 +0300:
> Hello Sean,
>
> EC2-api team always used manual tagging because I know only this procedure.
> I thought that it's more convenient for me cause I can manage
> commits/branches.
> But in fact I don't mind to switch to automatic scheme.
> If somethig else is needed from please let me know.
>
> Regards,
> Andrey Pavlov.
You will still need to trigger tags, you will just do it in a different
way. See
http://git.openstack.org/cgit/openstack/releases/tree/README.rst for
details and drop in to #openstack-release or send email to this list
with the subject tag "[release]" if you have any questions.
Doug
>
> >
>
> Hello teams,
>
> I am following up on some recently announced changes regarding governed
> projects and tagging rights. See [1] for background.
>
> It was mostly followed before that when a project came under official
> governance that all tagging and releases would then move to using the
> openstack/releases repo and associated automation. It was not officially stated
> until recently that this was one of the steps of coming under governance, so
> there were a few projects that became official but that continued to do their
> own releases.
>
> We've cleaned up most projects' rights to push tags, but for the ones listed
> here we waited:
>
> - rally
> - dragflow
> - ec2-api
> - networking-powervm
> - nova-powervm
> - yaql
>
> We would like to finish cleaning up the ACLs for these, but I wanted to check
> with the teams to make sure there wasn't a reason why these repos had continued
> tagging separately. Please let me know, either here or in the
> #openstack-release channel, if there is something we are overlooking.
>
> Thanks for your attention.
>
> ---
> Sean (smcginnis)
More information about the OpenStack-dev
mailing list