Re: [openstack-dev] [rally][dragonflow][ec2-api][PowerVMStackers][murano] Tagging rights

[Doug Hellmann]

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)

__
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] [rally][dragonflow][ec2-api][PowerVMStackers][murano] Tagging rights

[Andrey Pavlov]

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.

>

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)
__
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] [rally][dragonflow][ec2-api][PowerVMStackers][murano] Tagging rights

[Rong Zhu]

Hi Sean!

yaql is OK to this.


On Sat, Apr 14, 2018 at 3:46 AM, Sean McGinnis 
wrote:

> 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)
>
> __
> 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
>



-- 
Thanks,
Rong Zhu
__
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] [rally][dragonflow][ec2-api][PowerVMStackers][murano] Tagging rights

[Andrey Kurilin]

Hi Sean!

Thanks for raising this question.

As for Rally team, we are using self-tagging approach for several reasons:

- Release notes

  Check the difference between
https://github.com/openstack/nova/releases/tag/17.0.2 and
https://github.com/openstack/rally-openstack/releases/tag/1.0.0.
  The first one includes just autogenerated metadata. The second one
user-friendly notes (they are not ideal, but we are working on making them
better).
  I do not find a way to add custom release notes via openstack/releases
project.

- Time

  Self-tagging the repo allows me to schedule/reschedule the release in
whatever timeframe I decide without pinging anyone and waiting for folks to
return from summit/PTG.
  I do not want to offend anyone, but we all know that such events take
much time for preparation, holding and resting after it.

  Since there are no official OpenStack projects built on top of Rally,
launching any of "integration" jobs while making Rally release is a wasting
of time and money(resources).
  Also, such jobs can block to make a release. I remember sometimes it can
take weeks to pass all gates with tons of rechecks

  https://github.com/openstack/releases#release-approval == "Freezes and no
late releases". It is an opensource and I want to make releases on weekends
if there is any
  reason for doing this (critical fix or the last blocking feature is
merged or whatever).


2018-04-13 22:53 GMT+03:00 Sean McGinnis :

> On Fri, Apr 13, 2018 at 02:46:59PM -0500, Sean McGinnis wrote:
> > Hello teams,
> >
> > I am following up on some recently announced changes regarding governed
> > projects and tagging rights. See [1] for background.
> >
>
> [1] https://review.openstack.org/#/c/557737/
>
>
> __
> 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
>



-- 
Best regards,
Andrey Kurilin.
__
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] [rally][dragonflow][ec2-api][PowerVMStackers][murano] Tagging rights

[Sean McGinnis]

On Fri, Apr 13, 2018 at 02:46:59PM -0500, Sean McGinnis wrote:
> Hello teams,
> 
> I am following up on some recently announced changes regarding governed
> projects and tagging rights. See [1] for background.
> 

[1] https://review.openstack.org/#/c/557737/


__
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] [rally][dragonflow][ec2-api][PowerVMStackers][murano] Tagging rights

[Sean McGinnis]

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)

__
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