Re: [openstack-dev] [all][infra] Automatically generated Zuul changes (topic: zuulv3-projects)

2018-02-05 Thread Andreas Jaeger 
Please accept these changes so that they don't have to be created for
the stable/queens branch,

Andreas

On 2018-01-31 18:59, James E. Blair wrote:
> Hi,
> 
> Occasionally we will make changes to the Zuul configuration language.
> Usually these changes will be backwards compatible, but whether they are
> or not, we still want to move things forward.
> 
> Because Zuul's configuration is now spread across many repositories, it
> may take many changes to do this.  I'm in the process of making one such
> change now.
> 
> Zuul no longer requires the project name in the "project:" stanza for
> in-repo configuration.  Removing it makes it easier to fork or rename a
> project.
> 
> I am using a script to create and upload these changes.  Because changes
> to Zuul's configuration use more resources, I, and the rest of the infra
> team, are carefully monitoring this and pacing changes so as not to
> overwhelm the system.  This is a limitation we'd like to address in the
> future, but we have to live with now.
> 
> So if you see such a change to your project (the topic will be
> "zuulv3-projects"), please observe the following:
> 
> * Go ahead and approve it as soon as possible.
> 
> * Don't be strict about backported change ids.  These changes are only
>   to Zuul config files, the stable backport policy was not intended to
>   apply to things like this.
> 
> * Don't create your own versions of these changes.  My script will
>   eventually upload changes to all affected project-branches.  It's
>   intentionally a slow process, and attempting to speed it up won't
>   help.  But if there's something wrong with the change I propose, feel
>   free to push an update to correct it.


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] [all][infra] Automatically generated Zuul changes (topic: zuulv3-projects)

2018-01-31 Thread Andreas Jaeger 
On 2018-02-01 05:49, Takashi Yamamoto wrote:
> [...]
>> * Don't create your own versions of these changes.  My script will
>>   eventually upload changes to all affected project-branches.  It's
>>   intentionally a slow process, and attempting to speed it up won't
>>   help.  But if there's something wrong with the change I propose, feel
>>   free to push an update to correct it.
> 1. is it ok to create my version of the change when making other
> changes to the file?  eg. https://review.openstack.org/#/c/538200/


If you add a *new* zuul.yaml file, do not add the project name stanza.
His scripts will not catch new additions.

If you change an existing file, wait for Jim's change.

> 2. as a reviewer, what should i do to the similar changes which is not yours?
> https://review.openstack.org/#/q/topic:zuulv3-projects+NOT+owner:%22James+E.+Blair+%253Ccorvus%2540inaugust.com%253E%22

I would block any new ones with a reference to the message. There's
really no sense in doing those changes and cause extra work,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
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] [all][infra] Automatically generated Zuul changes (topic: zuulv3-projects)

2018-01-31 Thread Takashi Yamamoto 
On Thu, Feb 1, 2018 at 2:59 AM, James E. Blair  wrote:
> Hi,
>
> Occasionally we will make changes to the Zuul configuration language.
> Usually these changes will be backwards compatible, but whether they are
> or not, we still want to move things forward.
>
> Because Zuul's configuration is now spread across many repositories, it
> may take many changes to do this.  I'm in the process of making one such
> change now.
>
> Zuul no longer requires the project name in the "project:" stanza for
> in-repo configuration.  Removing it makes it easier to fork or rename a
> project.
>
> I am using a script to create and upload these changes.  Because changes
> to Zuul's configuration use more resources, I, and the rest of the infra
> team, are carefully monitoring this and pacing changes so as not to
> overwhelm the system.  This is a limitation we'd like to address in the
> future, but we have to live with now.
>
> So if you see such a change to your project (the topic will be
> "zuulv3-projects"), please observe the following:
>
> * Go ahead and approve it as soon as possible.
>
> * Don't be strict about backported change ids.  These changes are only
>   to Zuul config files, the stable backport policy was not intended to
>   apply to things like this.
>
> * Don't create your own versions of these changes.  My script will
>   eventually upload changes to all affected project-branches.  It's
>   intentionally a slow process, and attempting to speed it up won't
>   help.  But if there's something wrong with the change I propose, feel
>   free to push an update to correct it.

1. is it ok to create my version of the change when making other
changes to the file?  eg. https://review.openstack.org/#/c/538200/

2. as a reviewer, what should i do to the similar changes which is not yours?
https://review.openstack.org/#/q/topic:zuulv3-projects+NOT+owner:%22James+E.+Blair+%253Ccorvus%2540inaugust.com%253E%22

>
> Thanks,
>
> Jim
>
> __
> 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 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] [all][infra] Automatically generated Zuul changes (topic: zuulv3-projects)

2018-01-31 Thread James E. Blair 
Hi,

Occasionally we will make changes to the Zuul configuration language.
Usually these changes will be backwards compatible, but whether they are
or not, we still want to move things forward.

Because Zuul's configuration is now spread across many repositories, it
may take many changes to do this.  I'm in the process of making one such
change now.

Zuul no longer requires the project name in the "project:" stanza for
in-repo configuration.  Removing it makes it easier to fork or rename a
project.

I am using a script to create and upload these changes.  Because changes
to Zuul's configuration use more resources, I, and the rest of the infra
team, are carefully monitoring this and pacing changes so as not to
overwhelm the system.  This is a limitation we'd like to address in the
future, but we have to live with now.

So if you see such a change to your project (the topic will be
"zuulv3-projects"), please observe the following:

* Go ahead and approve it as soon as possible.

* Don't be strict about backported change ids.  These changes are only
  to Zuul config files, the stable backport policy was not intended to
  apply to things like this.

* Don't create your own versions of these changes.  My script will
  eventually upload changes to all affected project-branches.  It's
  intentionally a slow process, and attempting to speed it up won't
  help.  But if there's something wrong with the change I propose, feel
  free to push an update to correct it.

Thanks,

Jim

__
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