Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Excerpts from Doug Hellmann's message of 2017-10-24 09:42:25 -0400: > The neutron queens milestone release is held up right now because > some of the repositories are using a release job template that isn't > recognized by the validation code in the releases repository. I'm > trying to decide

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

On 2017-10-24 16:24:39 -0700 (-0700), Armando M. wrote: [...] > I hope I represented the conversation correctly! [...] Totally accurate, thanks! -- Jeremy Stanley signature.asc Description: Digital signature __ OpenStack

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

On 24 October 2017 at 13:13, Jeremy Stanley wrote: > On 2017-10-24 11:31:56 -0700 (-0700), Armando M. wrote: > [...] > > the work on neutron-lib is slowly progressing but it's not close enough > to > > allow us to break the dependency that requires neutron sub-projects to >

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

On 2017-10-24 11:31:56 -0700 (-0700), Armando M. wrote: [...] > the work on neutron-lib is slowly progressing but it's not close enough to > allow us to break the dependency that requires neutron sub-projects to add > neutron to the list of required-projects (which I believe the sort of the >

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

On 24 October 2017 at 10:35, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2017-10-24 15:05:34 +: > > On 2017-10-24 09:42:25 -0400 (-0400), Doug Hellmann wrote: > > [...] > > > It looks like the publish-to-pypi-neutron template modifies > > >

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Excerpts from Jeremy Stanley's message of 2017-10-24 15:05:34 +: > On 2017-10-24 09:42:25 -0400 (-0400), Doug Hellmann wrote: > [...] > > It looks like the publish-to-pypi-neutron template modifies > > publish-to-pypi by adding openstack/neutron to the required-repositories > > list for the

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

On 2017-10-24 09:42:25 -0400 (-0400), Doug Hellmann wrote: [...] > It looks like the publish-to-pypi-neutron template modifies > publish-to-pypi by adding openstack/neutron to the required-repositories > list for the release-openstack-python job. That repository was also at > some point added

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Please see below: On Tue, Oct 24, 2017 at 10:11 AM, Thierry Carrez wrote: > Doug Hellmann wrote: >> [...] >> It feels like we have two related by not necessarily dependent >> policy questions we need to answer before we decide how to proceed: > > I don't have strong

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

On Tue, Oct 24, 2017 at 09:42:25AM -0400, Doug Hellmann wrote: > The neutron queens milestone release is held up right now because > some of the repositories are using a release job template that isn't > recognized by the validation code in the releases repository. I'm > trying to decide between

Re: [openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Doug Hellmann wrote: > [...] > It feels like we have two related by not necessarily dependent > policy questions we need to answer before we decide how to proceed: I don't have strong opinions on any of those two, I think anything would work. If I had to pick between yes and no, here is my gut