Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

2017-07-18 Thread Lance Bragstad 


On 07/18/2017 08:21 AM, Andy McCrae wrote:
>
>
>
> The branches have now been retired, thanks to Joshua Hesketh!
>
>
> Thanks Josh, Andreas, Tony, and the rest of the Infra crew for sorting
> this out.

++ thanks all!

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



signature.asc
Description: OpenPGP digital signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-07-18 Thread Andy McCrae 
>
>
>
> The branches have now been retired, thanks to Joshua Hesketh!
>

Thanks Josh, Andreas, Tony, and the rest of the Infra crew for sorting this
out.

Andy
__
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][stable][ptls] Tagging mitaka as EOL

2017-07-18 Thread Andreas Jaeger 
On 2017-07-17 19:09, Andreas Jaeger wrote:
> On 2017-07-17 15:51, Andy McCrae wrote:
>> We held back the openstack-ansible repo to allow us to point to the
>> mitaka-eol tag for the other role/project repos.
>> That's been done - I've created the mitaka-eol tag in the
>> openstack-ansible repo, can we remove the stable/mitaka branch from
>> openstack-ansible too.
> 
> So, only from openstack/openstack-ansible?
> 
>> Thanks again to all who have helped EOL all the branches etc!
> 
> I'll add to the list,
> 
> Andreas
> 

The branches have now been retired, thanks to Joshua Hesketh!

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][stable][ptls] Tagging mitaka as EOL

2017-07-17 Thread Tony Breeds 
On Mon, Jul 17, 2017 at 07:09:13PM +0200, Andreas Jaeger wrote:
> On 2017-07-17 15:51, Andy McCrae wrote:
> > We held back the openstack-ansible repo to allow us to point to the
> > mitaka-eol tag for the other role/project repos.
> > That's been done - I've created the mitaka-eol tag in the
> > openstack-ansible repo, can we remove the stable/mitaka branch from
> > openstack-ansible too.
> 
> So, only from openstack/openstack-ansible?

Yup that was left so it could include the taggs for the service projects
and roles.

> > Thanks again to all who have helped EOL all the branches etc!
> 
> I'll add to the list,

Thanks.
Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-07-17 Thread Andreas Jaeger 
On 2017-07-17 15:51, Andy McCrae wrote:
> We held back the openstack-ansible repo to allow us to point to the
> mitaka-eol tag for the other role/project repos.
> That's been done - I've created the mitaka-eol tag in the
> openstack-ansible repo, can we remove the stable/mitaka branch from
> openstack-ansible too.

So, only from openstack/openstack-ansible?

> Thanks again to all who have helped EOL all the branches etc!

I'll add to the list,

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][stable][ptls] Tagging mitaka as EOL

2017-07-17 Thread Andy McCrae 
Hi Andreas,

OK, added. I'm waiting for packstack confirmation.
>
> The current list is now:
>
>
> openstack/sahara-extra   stable/icehousePlease retire
> openstack/sahara-extra   stable/mitaka  Please retire
> openstack/packstack  stable/kiloWaiting for confirmation
> openstack/packstack  stable/liberty Waiting for confirmation
> openstack/packstack  stable/mitaka  Waiting for confirmation
> openstack/bareon-ironic  stable/mitaka  Please retire
>
> openstack/rpm-packaging  stable/mitaka  Please retire
> openstack/training-labs  stable/mitaka  Please retire
>
> Not done in
> https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783b
> e7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt
>
> openstack/astara stable/mitaka  Please retire
>
>
> Special treatment:
> openstack/training-labs icehouse-eol (just delete branch, tag exists)
> openstack/training-labs juno-eol (delete branch, create tag instead)
>
>
> Any other late comers?
>
> We held back the openstack-ansible repo to allow us to point to the
mitaka-eol tag for the other role/project repos.
That's been done - I've created the mitaka-eol tag in the openstack-ansible
repo, can we remove the stable/mitaka branch from openstack-ansible too.

Thanks again to all who have helped EOL all the branches etc!
Andy
__
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][stable][ptls] Tagging mitaka as EOL

2017-07-11 Thread Tony Breeds 
On Mon, Jul 10, 2017 at 11:33:51AM +, Gary Kotton wrote:
> Hi,
> Will this also be moving to eol -
> https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt?

We need to be very careful EOLing that repo (if at all) as project have
deep links to the upper-constratints.txt files in that repo.
If we remove that branch they'll all break and with a couple of
different behaviours (depending on pip version).  It's a corner case but
one we can avoid :D

I think we'll do (tagg EOL) devstack once we're sure all gate jobs
aren't using it.

Tony.



signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-07-10 Thread Andreas Jaeger 
On 2017-07-10 13:33, Gary Kotton wrote:
> Hi,
> Will this also be moving to eol - 
> https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt?

No, not planned yet,

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][stable][ptls] Tagging mitaka as EOL

2017-07-10 Thread Gary Kotton 
Hi,
Will this also be moving to eol - 
https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt?
Thanks
Gary

On 7/10/17, 9:23 AM, "Andreas Jaeger"  wrote:

On 2017-07-07 17:37, Doug Szumski wrote:
> 
>> On 2017-07-05 12:13, Joshua Hesketh wrote:
>>> Hi all,
>>>
>>> Very sorry for the delay on processing this request. I have now EOL'd 
>>> stable/mitaka branches for projects listed in [1].
>>>
>>> If there are any mistakes it should be possible to restore the branch 
>>> at the correct position. Similarly please let me know if there were 
>>> any projects that should have been EOL'd but missed out.
> 
> Please also remove stable/mitaka from bareon-ironic

OK, added. I'm waiting for packstack confirmation.

The current list is now:


openstack/sahara-extra   stable/icehousePlease retire
openstack/sahara-extra   stable/mitaka  Please retire
openstack/packstack  stable/kiloWaiting for confirmation
openstack/packstack  stable/liberty Waiting for confirmation
openstack/packstack  stable/mitaka  Waiting for confirmation
openstack/bareon-ironic  stable/mitaka  Please retire

openstack/rpm-packaging  stable/mitaka  Please retire
openstack/training-labs  stable/mitaka  Please retire

Not done in

https://urldefense.proofpoint.com/v2/url?u=https-3A__gist.githubusercontent.com_tbreeds_c99e62bf8da19380e4eb130be8783be7_raw_6d02deb40e07516ce8fc529d2ba8c74af11a5a6b_mitaka-5Feol-5Fdata.txt=DwIGaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=8JDeI5-ToCWlT4wlMOEK26WybSrP1mfZXQUx_wH4Yvo=y5Ib3yOnStYUMsnSZ62_ZUm0zbcLuqrk34Hfk1mVORA=
 

openstack/astara stable/mitaka  Please retire


Special treatment:
openstack/training-labs icehouse-eol (just delete branch, tag exists)
openstack/training-labs juno-eol (delete branch, create tag instead)


Any other late comers?

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


__
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][stable][ptls] Tagging mitaka as EOL

2017-07-10 Thread Andreas Jaeger 
On 2017-07-07 17:37, Doug Szumski wrote:
> 
>> On 2017-07-05 12:13, Joshua Hesketh wrote:
>>> Hi all,
>>>
>>> Very sorry for the delay on processing this request. I have now EOL'd 
>>> stable/mitaka branches for projects listed in [1].
>>>
>>> If there are any mistakes it should be possible to restore the branch 
>>> at the correct position. Similarly please let me know if there were 
>>> any projects that should have been EOL'd but missed out.
> 
> Please also remove stable/mitaka from bareon-ironic

OK, added. I'm waiting for packstack confirmation.

The current list is now:


openstack/sahara-extra   stable/icehousePlease retire
openstack/sahara-extra   stable/mitaka  Please retire
openstack/packstack  stable/kiloWaiting for confirmation
openstack/packstack  stable/liberty Waiting for confirmation
openstack/packstack  stable/mitaka  Waiting for confirmation
openstack/bareon-ironic  stable/mitaka  Please retire

openstack/rpm-packaging  stable/mitaka  Please retire
openstack/training-labs  stable/mitaka  Please retire

Not done in
https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt

openstack/astara stable/mitaka  Please retire


Special treatment:
openstack/training-labs icehouse-eol (just delete branch, tag exists)
openstack/training-labs juno-eol (delete branch, create tag instead)


Any other late comers?

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][stable][ptls] Tagging mitaka as EOL

2017-07-07 Thread Doug Szumski 

> On 2017-07-05 12:13, Joshua Hesketh wrote:
> > Hi all,
> > 
> > Very sorry for the delay on processing this request. I have now EOL'd 
> > stable/mitaka branches for projects listed in [1].
> > 
> > If there are any mistakes it should be possible to restore the branch 
> > at the correct position. Similarly please let me know if there were 
> > any projects that should have been EOL'd but missed out.

Please also remove stable/mitaka from bareon-ironic

>
> astara was in the list but not done,
>
> I'm curently writing up a list of late-comers, if anybody has requests, sent 
> them my way this week, please,
>
> Andreas

__
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][stable][ptls] Tagging mitaka as EOL

2017-07-06 Thread Andreas Jaeger 
On 2017-07-05 12:13, Joshua Hesketh wrote:
> Hi all,
> 
> Very sorry for the delay on processing this request. I have now EOL'd
> stable/mitaka branches for projects listed in [1].
> 
> If there are any mistakes it should be possible to restore the branch at
> the correct position. Similarly please let me know if there were any
> projects that should have been EOL'd but missed out.

astara was in the list but not done,

I'm curently writing up a list of late-comers, if anybody has requests,
sent them my way this week, please,

Andreas

> Cheers,
> Josh
> 
> [1] 
> https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt
> 
> 
> On Thu, Jun 29, 2017 at 10:57 PM, Jeremy Stanley  > wrote:
> 
> On 2017-06-29 11:28:10 +1000 (+1000), Tony Breeds wrote:
> [...]
> > In the meantime we could look at adding permissions such that the Stable
> > PTL (Well actually I guess eventually it'd be the same bot that does the
> > release tagging) can push tags and abandon changes on all projects.
> >
> > Right now stable-maint-core can do that in a lot of projects but the
> > coverage isn't complete.
> 
> Sure, we just need to set it in the global configuration instead of
> on a per-project basis.
> 
> > That would allow us to make forward progress and reduce the task for the
> > infra team to deleting the branches.  It does of course introduce a
> > race where I could tag a branch as EOL and then that project merge
> > another change.  Can you think of a way to avoid that?
> 
> Not a convenient one anyway... we could probably merge (hundreds of)
> ACL changes preventing approvals on that branch for the projects
> participating in the EOL process, but that's probably worse than
> accepting that there might be a patch or two created, reviewed and
> landed on some project between the EOL tag and branch deletion. The
> additional changes that merge after the tag won't effectively be
> reachable once the branch is gone anyway (you could hunt them down
> in Gerrit, but there's no longer a branch in Git containing them an
> they're not in the history of any tag at that point). It's probably
> neither common nor disruptive enough to be worth our concern.
> --
> Jeremy Stanley
> 
> __
> 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
> 


-- 
 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][stable][ptls] Tagging mitaka as EOL

2017-07-06 Thread Andreas Jaeger 
On 2017-07-05 12:13, Joshua Hesketh wrote:
> Hi all,
> 
> Very sorry for the delay on processing this request. I have now EOL'd
> stable/mitaka branches for projects listed in [1].
> 
> If there are any mistakes it should be possible to restore the branch at
> the correct position. Similarly please let me know if there were any
> projects that should have been EOL'd but missed out.

Thanks, Joshua!

Infra team is currently removing all now obsolete jobs - trusty jobs on
projects that have no mitaka branch.

This shouldn't cause any changes to your setup - but if it does, please
reach out to us,

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][stable][ptls] Tagging mitaka as EOL

2017-07-05 Thread Joshua Hesketh 
Hi all,

Very sorry for the delay on processing this request. I have now EOL'd
stable/mitaka branches for projects listed in [1].

If there are any mistakes it should be possible to restore the branch at
the correct position. Similarly please let me know if there were any
projects that should have been EOL'd but missed out.

Cheers,
Josh

[1] https://gist.githubusercontent.com/tbreeds/c99e62bf8da19
380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a
5a6b/mitaka_eol_data.txt

On Thu, Jun 29, 2017 at 10:57 PM, Jeremy Stanley  wrote:

> On 2017-06-29 11:28:10 +1000 (+1000), Tony Breeds wrote:
> [...]
> > In the meantime we could look at adding permissions such that the Stable
> > PTL (Well actually I guess eventually it'd be the same bot that does the
> > release tagging) can push tags and abandon changes on all projects.
> >
> > Right now stable-maint-core can do that in a lot of projects but the
> > coverage isn't complete.
>
> Sure, we just need to set it in the global configuration instead of
> on a per-project basis.
>
> > That would allow us to make forward progress and reduce the task for the
> > infra team to deleting the branches.  It does of course introduce a
> > race where I could tag a branch as EOL and then that project merge
> > another change.  Can you think of a way to avoid that?
>
> Not a convenient one anyway... we could probably merge (hundreds of)
> ACL changes preventing approvals on that branch for the projects
> participating in the EOL process, but that's probably worse than
> accepting that there might be a patch or two created, reviewed and
> landed on some project between the EOL tag and branch deletion. The
> additional changes that merge after the tag won't effectively be
> reachable once the branch is gone anyway (you could hunt them down
> in Gerrit, but there's no longer a branch in Git containing them an
> they're not in the history of any tag at that point). It's probably
> neither common nor disruptive enough to be worth our concern.
> --
> Jeremy Stanley
>
> __
> 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

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

2017-06-29 Thread Jeremy Stanley 
On 2017-06-29 11:28:10 +1000 (+1000), Tony Breeds wrote:
[...]
> In the meantime we could look at adding permissions such that the Stable
> PTL (Well actually I guess eventually it'd be the same bot that does the
> release tagging) can push tags and abandon changes on all projects.
> 
> Right now stable-maint-core can do that in a lot of projects but the
> coverage isn't complete.

Sure, we just need to set it in the global configuration instead of
on a per-project basis.

> That would allow us to make forward progress and reduce the task for the
> infra team to deleting the branches.  It does of course introduce a
> race where I could tag a branch as EOL and then that project merge
> another change.  Can you think of a way to avoid that?

Not a convenient one anyway... we could probably merge (hundreds of)
ACL changes preventing approvals on that branch for the projects
participating in the EOL process, but that's probably worse than
accepting that there might be a patch or two created, reviewed and
landed on some project between the EOL tag and branch deletion. The
additional changes that merge after the tag won't effectively be
reachable once the branch is gone anyway (you could hunt them down
in Gerrit, but there's no longer a branch in Git containing them an
they're not in the history of any tag at that point). It's probably
neither common nor disruptive enough to be worth our concern.
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-06-28 Thread Tony Breeds 
On Wed, Jun 28, 2017 at 11:50:34PM +, Jeremy Stanley wrote:

> Indeed, that's a bummer. I hadn't noticed it until you pointed it
> out and assumed it had made it into the 2.13 series. Well, we're
> planning to look at logistics for a 2.14 upgrade soon once 2.13 is
> (hopefully!) in production, we just didn't want to backtrack and
> lose forward momentum on the current upgrade train. The transition
> to 2.14 will probably be a bit messy what with needing newer Java,
> which is why we can't adjust our plans easily at this stage.

In the meantime we could look at adding permissions such that the Stable
PTL (Well actually I guess eventually it'd be the same bot that does the
release tagging) can push tags and abandon changes on all projects.

Right now stable-maint-core can do that in a lot of projects but the
coverage isn't complete.

That would allow us to make forward progress and reduce the task for the
infra team to deleting the branches.  It does of course introduce a
race where I could tag a branch as EOL and then that project merge
another change.  Can you think of a way to avoid that?

Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-06-28 Thread Jeremy Stanley 
On 2017-06-28 13:21:46 +1000 (+1000), Tony Breeds wrote:
> On Tue, Jun 27, 2017 at 08:59:27PM +, Jeremy Stanley wrote:
> 
> > Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and
> > resume that much needed development effort.
> 
> This looks to have landed in 2.14[1] :(   I don't know how hard it'd be
> to backport to 2.13 or even if that's a thing we'd do.
> 
> It certainly doesn't cleanly cherry-pick :(
> 
> Yours Tony.
> 
> [1] https://gerrit-review.googlesource.com/c/85512

Indeed, that's a bummer. I hadn't noticed it until you pointed it
out and assumed it had made it into the 2.13 series. Well, we're
planning to look at logistics for a 2.14 upgrade soon once 2.13 is
(hopefully!) in production, we just didn't want to backtrack and
lose forward momentum on the current upgrade train. The transition
to 2.14 will probably be a bit messy what with needing newer Java,
which is why we can't adjust our plans easily at this stage.
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-06-27 Thread Joshua Hesketh 
On Wed, Jun 28, 2017 at 6:59 AM, Jeremy Stanley  wrote:

> On 2017-06-17 01:20:28 +1000 (+1000), Joshua Hesketh wrote:
> [...]
> > I'm happy to help do this if you'd like. Otherwise the script I've
> > used for the last few retirements is here:
> > http://git.openstack.org/cgit/openstack-infra/release-tools/
> tree/eol_branch.sh
>
> That would be really appreciated if you have the available
> bandwidth. If not, I'm going to try to find an opportunity to
> babysit it sometime later this week.
>


Yep, more than happy to. I'll try and get to it this week but if not, next
week at the latest.

Cheers,
Josh



>
> > I believe the intention was to add some hardening around that
> > script and automate it. However I think it was put on hold
> > awaiting a new gerrit.. either that or nobody took it up.
>
> Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and
> resume that much needed development effort.
> --
> Jeremy Stanley
>
> __
> 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

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

2017-06-27 Thread Tony Breeds 
On Tue, Jun 27, 2017 at 08:59:27PM +, Jeremy Stanley wrote:

> Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and
> resume that much needed development effort.

This looks to have landed in 2.14[1] :(   I don't know how hard it'd be
to backport to 2.13 or even if that's a thing we'd do.

It certainly doesn't cleanly cherry-pick :(

Yours Tony.

[1] https://gerrit-review.googlesource.com/c/85512


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-06-27 Thread Jeremy Stanley 
On 2017-06-17 01:20:28 +1000 (+1000), Joshua Hesketh wrote:
[...]
> I'm happy to help do this if you'd like. Otherwise the script I've
> used for the last few retirements is here:
> http://git.openstack.org/cgit/openstack-infra/release-tools/tree/eol_branch.sh

That would be really appreciated if you have the available
bandwidth. If not, I'm going to try to find an opportunity to
babysit it sometime later this week.

> I believe the intention was to add some hardening around that
> script and automate it. However I think it was put on hold
> awaiting a new gerrit.. either that or nobody took it up.

Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and
resume that much needed development effort.
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-06-18 Thread Tony Breeds 
On Fri, Jun 16, 2017 at 02:14:59PM +, Jeremy Stanley wrote:
> On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote:
> [...]
> > It seeems a little odd to be following up so long after I first started
> > this thread  but can someone on infra please process the EOLs as
> > described in [1].
> [...]
> 
> I thought in prior discussions it had been determined that the
> Stable Branch team was going to start taking care of abandoning open
> changes and tagging branch tips (and eventually deleting the
> branches once we upgrade to a newer Gerrit release).

That was the plan but as you point out the removal of branches is
blocked on a new gerrit release.  The stable team is lacking permissions
to abandon reviews on several projects so it's the infra script needs to
handle the abandoning of open reviews and the tagging anyway so I
stopped doing those bits until we can progress the whole thing.  Perhaps
that's a poor choice and I'd be very happy to re-visit it.

>  Looks like some
> of these still have open changes and nothing has been tagged, so you
> want the Infra team to take those tasks back over for this round?
> Did you have any scripts you wanted used for this, or should I just
> wing it for now like I did in the past?

Josh wrote a script[1] to do it which IMO has worked well in the last 2
cycles.  You can do something like:

URL='https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt'
eol_branch.sh stable/mitaka mitaka-eol $( curl -s "$URL" | awk '/Please EOL/ 
{print $1}' )

Yours Tony.

[1] 
http://git.openstack.org/cgit/openstack-infra/release-tools/tree/eol_branch.sh


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-06-16 Thread Joshua Hesketh 
On Sat, Jun 17, 2017 at 12:14 AM, Jeremy Stanley  wrote:

> On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote:
> [...]
> > It seeems a little odd to be following up so long after I first started
> > this thread  but can someone on infra please process the EOLs as
> > described in [1].
> [...]
>
> I thought in prior discussions it had been determined that the
> Stable Branch team was going to start taking care of abandoning open
> changes and tagging branch tips (and eventually deleting the
> branches once we upgrade to a newer Gerrit release). Looks like some
> of these still have open changes and nothing has been tagged, so you
> want the Infra team to take those tasks back over for this round?
> Did you have any scripts you wanted used for this, or should I just
> wing it for now like I did in the past?
>

I'm happy to help do this if you'd like. Otherwise the script I've used for
the last few retirements is here:
http://git.openstack.org/cgit/openstack-infra/release-tools/tree/eol_branch.sh

I believe the intention was to add some hardening around that script and
automate it. However I think it was put on hold awaiting a new gerrit..
either that or nobody took it up.

Cheers,
Josh



> --
> Jeremy Stanley
>
> __
> 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

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

2017-06-16 Thread Jeremy Stanley 
On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote:
[...]
> It seeems a little odd to be following up so long after I first started
> this thread  but can someone on infra please process the EOLs as
> described in [1].
[...]

I thought in prior discussions it had been determined that the
Stable Branch team was going to start taking care of abandoning open
changes and tagging branch tips (and eventually deleting the
branches once we upgrade to a newer Gerrit release). Looks like some
of these still have open changes and nothing has been tagged, so you
want the Infra team to take those tasks back over for this round?
Did you have any scripts you wanted used for this, or should I just
wing it for now like I did in the past?
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-06-15 Thread Tony Breeds 
On Wed, Apr 12, 2017 at 04:47:25PM +1000, Tony Breeds wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
> 
> I'm proposing to EOL all projects that meet one or more of the following
> criteria:
> 
> - The project is openstack-dev/devstack, openstack-dev/grenade or
>   openstack/requirements
> - The project has the 'check-requirements' job listed as a template in
>   project-config:zuul/layout.yaml
> - The project gates with either devstack or grenade jobs
> - The project is listed in governance:reference/projects.yaml and is tagged
>   with 'stable:follows-policy'.
> 
> Some statistics:
> All Repos  : 1584 (covered in zuul/layout.yaml)
> Checked Repos  :  416 (match one or more of the above 
> criteria)
> Repos with mitaka branches :  409
> EOL Repos  :  199 (repos that match the criteria *and* 
> have
>a mitaka branch) [1]
> NOT EOL Repos  :  210 (repos with a mitaka branch but
>otherwise do not match) [2]
> DSVM Repos (staying)   :   68 (repos that use dsvm but don't have
>mitaka branches)
> Tagged Repos   :0
> Open Reviews   :  159 (reviews to close)
> 
> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
> - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing 
> and
>   why.  Note doing this will amost certainly reduce the testing coverage you
>   have in the gate.
> - A project is in list 2 that would like to opt *IN* to tagging/EOLing
> 
> Any projects that will be EOL'd will need all open reviews abandoned before it
> can be processed.  I'm very happy to do this, or if I don't have permissios to
> do it ask a gerrit admin to do it.

It seeems a little odd to be following up so long after I first started
this thread  but can someone on infra please process the EOLs as
described in [1].

Yours Tony.

[1] 
https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-28 Thread Emilien Macchi 
On Mon, Apr 24, 2017 at 10:43 PM, Emilien Macchi  wrote:
> On Mon, Apr 17, 2017 at 1:03 PM, Emilien Macchi  wrote:
>> On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds  wrote:
>>> Hi all,
>>> I'm late in sending this announement, but I'm glad to see several 
>>> projects
>>> have already requested EOL releases to make it trivial and obvious where to
>>> apply the tag.
>>>
>>> I'm proposing to EOL all projects that meet one or more of the following
>>> criteria:
>>>
>>> - The project is openstack-dev/devstack, openstack-dev/grenade or
>>>   openstack/requirements
>>> - The project has the 'check-requirements' job listed as a template in
>>>   project-config:zuul/layout.yaml
>>> - The project gates with either devstack or grenade jobs
>>> - The project is listed in governance:reference/projects.yaml and is tagged
>>>   with 'stable:follows-policy'.
>>>
>>> Some statistics:
>>> All Repos  : 1584 (covered in zuul/layout.yaml)
>>> Checked Repos  :  416 (match one or more of the above 
>>> criteria)
>>> Repos with mitaka branches :  409
>>> EOL Repos  :  199 (repos that match the criteria *and* 
>>> have
>>>a mitaka branch) [1]
>>> NOT EOL Repos  :  210 (repos with a mitaka branch but
>>>otherwise do not match) [2]
>>> DSVM Repos (staying)   :   68 (repos that use dsvm but don't have
>>>mitaka branches)
>>> Tagged Repos   :0
>>> Open Reviews   :  159 (reviews to close)
>>>
>>> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
>>> - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing 
>>> and
>>>   why.  Note doing this will amost certainly reduce the testing coverage you
>>>   have in the gate.
>>> - A project is in list 2 that would like to opt *IN* to tagging/EOLing
>>>
>>> Any projects that will be EOL'd will need all open reviews abandoned before 
>>> it
>>> can be processed.  I'm very happy to do this, or if I don't have permissios 
>>> to
>>> do it ask a gerrit admin to do it.
>>
>> Please EOL stable/mitaka for:
>> - instack-undercloud (and featureV2/juno/kilo old branches)
>> - tripleo-heat-templates (and icehouse)
>> - tripleo-puppet-elements
>> - puppet-tripleo
>> - tripleo-image-elements (just featureV2)
>> - python-tripleoclient
>> - tripleo-common
>
> I'll take care of EOLing them, after reading latest email from Tony.
> I would need some help from infra to remove the branches I mentioned ^
> please (featureV2, juno, kilo, icehouse).
>
> I'll keep you posted on my progress.

EOLing for TripleO has been processed.
Big thanks to fungi & Ajaeger for their precious help here.

>> Thanks,
>>
>>> Yours Tony.
>>>
>>> [1] 
>>> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L1
>>> [2] 
>>> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L209
>>>
>>> __
>>> 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
>>>
>>
>>
>>
>> --
>> Emilien Macchi
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi

__
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][stable][ptls] Tagging mitaka as EOL

2017-04-24 Thread Emilien Macchi 
On Mon, Apr 17, 2017 at 1:03 PM, Emilien Macchi  wrote:
> On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds  wrote:
>> Hi all,
>> I'm late in sending this announement, but I'm glad to see several 
>> projects
>> have already requested EOL releases to make it trivial and obvious where to
>> apply the tag.
>>
>> I'm proposing to EOL all projects that meet one or more of the following
>> criteria:
>>
>> - The project is openstack-dev/devstack, openstack-dev/grenade or
>>   openstack/requirements
>> - The project has the 'check-requirements' job listed as a template in
>>   project-config:zuul/layout.yaml
>> - The project gates with either devstack or grenade jobs
>> - The project is listed in governance:reference/projects.yaml and is tagged
>>   with 'stable:follows-policy'.
>>
>> Some statistics:
>> All Repos  : 1584 (covered in zuul/layout.yaml)
>> Checked Repos  :  416 (match one or more of the above 
>> criteria)
>> Repos with mitaka branches :  409
>> EOL Repos  :  199 (repos that match the criteria *and* 
>> have
>>a mitaka branch) [1]
>> NOT EOL Repos  :  210 (repos with a mitaka branch but
>>otherwise do not match) [2]
>> DSVM Repos (staying)   :   68 (repos that use dsvm but don't have
>>mitaka branches)
>> Tagged Repos   :0
>> Open Reviews   :  159 (reviews to close)
>>
>> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
>> - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing 
>> and
>>   why.  Note doing this will amost certainly reduce the testing coverage you
>>   have in the gate.
>> - A project is in list 2 that would like to opt *IN* to tagging/EOLing
>>
>> Any projects that will be EOL'd will need all open reviews abandoned before 
>> it
>> can be processed.  I'm very happy to do this, or if I don't have permissios 
>> to
>> do it ask a gerrit admin to do it.
>
> Please EOL stable/mitaka for:
> - instack-undercloud (and featureV2/juno/kilo old branches)
> - tripleo-heat-templates (and icehouse)
> - tripleo-puppet-elements
> - puppet-tripleo
> - tripleo-image-elements (just featureV2)
> - python-tripleoclient
> - tripleo-common

I'll take care of EOLing them, after reading latest email from Tony.
I would need some help from infra to remove the branches I mentioned ^
please (featureV2, juno, kilo, icehouse).

I'll keep you posted on my progress.

> Thanks,
>
>> Yours Tony.
>>
>> [1] 
>> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L1
>> [2] 
>> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L209
>>
>> __
>> 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
>>
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi

__
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][stable][ptls] Tagging mitaka as EOL

2017-04-17 Thread Tony Breeds 
On Mon, Apr 17, 2017 at 09:55:51AM -0400, Brian Rosmaita wrote:
> On 4/12/17 2:47 AM, Tony Breeds wrote:
> > Hi all,
> > I'm late in sending this announement, but I'm glad to see several 
> > projects
> > have already requested EOL releases to make it trivial and obvious where to
> > apply the tag.
> > 
> > I'm proposing to EOL all projects ...
> 
> Hi Tony, just wanted to give you a glance update.
> 
> We need to backport a fix to stable/mitaka glance_store and cut a
> release before it gets EOL'd.  That will cascade back onto a need to cut
> a new glance in stable/mitaka with the updated requirement.  We should
> be able to get this done this week.

Okay, I'm a little worried that what you describe sounds like a minimum version
bump which isn't a thing we do on stable branches.  Do you have open reviews,
even if they're -W'd?

Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-17 Thread Emilien Macchi 
On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds  wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
>
> I'm proposing to EOL all projects that meet one or more of the following
> criteria:
>
> - The project is openstack-dev/devstack, openstack-dev/grenade or
>   openstack/requirements
> - The project has the 'check-requirements' job listed as a template in
>   project-config:zuul/layout.yaml
> - The project gates with either devstack or grenade jobs
> - The project is listed in governance:reference/projects.yaml and is tagged
>   with 'stable:follows-policy'.
>
> Some statistics:
> All Repos  : 1584 (covered in zuul/layout.yaml)
> Checked Repos  :  416 (match one or more of the above 
> criteria)
> Repos with mitaka branches :  409
> EOL Repos  :  199 (repos that match the criteria *and* 
> have
>a mitaka branch) [1]
> NOT EOL Repos  :  210 (repos with a mitaka branch but
>otherwise do not match) [2]
> DSVM Repos (staying)   :   68 (repos that use dsvm but don't have
>mitaka branches)
> Tagged Repos   :0
> Open Reviews   :  159 (reviews to close)
>
> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
> - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing 
> and
>   why.  Note doing this will amost certainly reduce the testing coverage you
>   have in the gate.
> - A project is in list 2 that would like to opt *IN* to tagging/EOLing
>
> Any projects that will be EOL'd will need all open reviews abandoned before it
> can be processed.  I'm very happy to do this, or if I don't have permissios to
> do it ask a gerrit admin to do it.

Please EOL stable/mitaka for:
- instack-undercloud (and featureV2/juno/kilo old branches)
- tripleo-heat-templates (and icehouse)
- tripleo-puppet-elements
- puppet-tripleo
- tripleo-image-elements (just featureV2)
- python-tripleoclient
- tripleo-common

Thanks,

> Yours Tony.
>
> [1] 
> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L1
> [2] 
> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L209
>
> __
> 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
>



-- 
Emilien Macchi

__
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][stable][ptls] Tagging mitaka as EOL

2017-04-17 Thread Brian Rosmaita 
On 4/12/17 2:47 AM, Tony Breeds wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
> 
> I'm proposing to EOL all projects ...

Hi Tony, just wanted to give you a glance update.

We need to backport a fix to stable/mitaka glance_store and cut a
release before it gets EOL'd.  That will cascade back onto a need to cut
a new glance in stable/mitaka with the updated requirement.  We should
be able to get this done this week.

cheers,
brian

__
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][stable][ptls] Tagging mitaka as EOL

2017-04-14 Thread Tony Breeds 
On Thu, Apr 13, 2017 at 04:58:12PM -0700, Samuel Cassiba wrote:
> Hi Tony,
> 
> I’m not the PTL, but I asked in our channel. You can EOL Chef OpenStack as 
> well. Thanks!

Cool.

I've added the Chef repos to the EOL list.

Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-13 Thread Tony Breeds 
On Thu, Apr 13, 2017 at 04:48:34PM -0700, Sumit Naiksatam wrote:
> Hi Tony, Kindly do not EOL openstack/group-based-policy, we are
> maintaining this branch.

Done.

Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-13 Thread Samuel Cassiba 
Hi Tony,

I’m not the PTL, but I asked in our channel. You can EOL Chef OpenStack as 
well. Thanks!

--
Best,

Samuel Cassiba


signature.asc
Description: Message signed with OpenPGP
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-13 Thread Sumit Naiksatam 
Hi Tony, Kindly do not EOL openstack/group-based-policy, we are
maintaining this branch.

Thanks,
~Sumit.



On Thu, Apr 13, 2017 at 4:40 PM, Tony Breeds  wrote:
> On Thu, Apr 13, 2017 at 08:20:50AM -0600, Alex Schultz wrote:
>
>> I would not include puppet-midonet without verification from those
>> devs. I believe it is still in use.
>
> Okay I'll leave them in the NOT EOLing list.  I assumed that puppet-midonet
> would just plain fail once there wasn't a stable/mitaka branch in the otehr
> repos.
>
> Yours Tony.
>
> __
> 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

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

2017-04-13 Thread Tony Breeds 
On Thu, Apr 13, 2017 at 03:55:56PM +0100, Andy McCrae wrote:

> Can the openstack-ansible repository be skipped until other repo's are
> EOL'd, please? The reason is that we'd like the mitaka-eol tag for OSA to
> point to the mitaka-eol tag of the appropriate upstream projects, in order
> for that to happen those tags need to exist. That would mean we need an
> extra week or so. This would just be for the openstack-ansible integrated
> repository, and not for all the other role repositories, those can be eol'd
> as normal.

Yup no problem.  I'll modify my script to handle cycle-trailing projects
in a seperate pass.

> For now I've gone ahead and abandoned open patches for the stable/mitaka
> branch on OSA repositories.

Thanks

Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-13 Thread Andy McCrae 
Hi Tony,


> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
> - A project is in list 1 and *really* *really* wants to opt *OUT* of
> EOLing and
>   why.  Note doing this will amost certainly reduce the testing coverage
> you
>   have in the gate.
> - A project is in list 2 that would like to opt *IN* to tagging/EOLing
>
> Any projects that will be EOL'd will need all open reviews abandoned
> before it
> can be processed.  I'm very happy to do this, or if I don't have
> permissios to
> do it ask a gerrit admin to do it.
>
>
Can the openstack-ansible repository be skipped until other repo's are
EOL'd, please? The reason is that we'd like the mitaka-eol tag for OSA to
point to the mitaka-eol tag of the appropriate upstream projects, in order
for that to happen those tags need to exist. That would mean we need an
extra week or so. This would just be for the openstack-ansible integrated
repository, and not for all the other role repositories, those can be eol'd
as normal.

For now I've gone ahead and abandoned open patches for the stable/mitaka
branch on OSA repositories.

Thanks for the help!
Andy
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-13 Thread Alex Schultz 
On Wed, Apr 12, 2017 at 6:21 PM, Tony Breeds  wrote:
> On Wed, Apr 12, 2017 at 07:53:17AM -0600, Alex Schultz wrote:
>
>> Please EOL the Puppet OpenStack projects that have the stable/mitaka branch.
>
> Thanks Alex!  I've added:
> openstack/puppet-aodh
> openstack/puppet-ceilometer
> openstack/puppet-cinder
> openstack/puppet-designate
> openstack/puppet-glance
> openstack/puppet-gnocchi
> openstack/puppet-heat
> openstack/puppet-horizon
> openstack/puppet-ironic
> openstack/puppet-keystone
> openstack/puppet-manila
> openstack/puppet-mistral
> openstack/puppet-murano
> openstack/puppet-neutron
> openstack/puppet-nova
> openstack/puppet-openstack-integration
> openstack/puppet-openstack_extras
> openstack/puppet-openstack_spec_helper
> openstack/puppet-openstacklib
> openstack/puppet-sahara
> openstack/puppet-swift
> openstack/puppet-tempest
> openstack/puppet-trove
> openstack/puppet-vswitch
> openstack/puppet-zaqar
> openstack/puppet-midonet
>
> To the list of projects/repos to EOL.  Note openstack/puppet-midonet isn't 
> part
> of the "Puppet OpenStack" project but I'm erring on the side of including it.
>

I would not include puppet-midonet without verification from those
devs. I believe it is still in use.

Thanks,
-Alex

> Yours Tony.
>
> __
> 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

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

2017-04-12 Thread Tony Breeds 
On Wed, Apr 12, 2017 at 02:27:22PM +, gordon chung wrote:
> i imagine you can EOL python-aodhclient and ceilometermiddleware. thanks 

Thanks I've added those repos/projects.

Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-12 Thread Tony Breeds 
On Wed, Apr 12, 2017 at 04:06:36PM +0200, Andreas Jaeger wrote:
> Please add openstack-manuals to the list for EOL,

Thanks Added!

Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-12 Thread Tony Breeds 
On Wed, Apr 12, 2017 at 07:53:17AM -0600, Alex Schultz wrote:

> Please EOL the Puppet OpenStack projects that have the stable/mitaka branch.

Thanks Alex!  I've added:
openstack/puppet-aodh
openstack/puppet-ceilometer
openstack/puppet-cinder
openstack/puppet-designate
openstack/puppet-glance
openstack/puppet-gnocchi
openstack/puppet-heat
openstack/puppet-horizon
openstack/puppet-ironic
openstack/puppet-keystone
openstack/puppet-manila
openstack/puppet-mistral
openstack/puppet-murano
openstack/puppet-neutron
openstack/puppet-nova
openstack/puppet-openstack-integration
openstack/puppet-openstack_extras
openstack/puppet-openstack_spec_helper
openstack/puppet-openstacklib
openstack/puppet-sahara
openstack/puppet-swift
openstack/puppet-tempest
openstack/puppet-trove
openstack/puppet-vswitch
openstack/puppet-zaqar
openstack/puppet-midonet

To the list of projects/repos to EOL.  Note openstack/puppet-midonet isn't part
of the "Puppet OpenStack" project but I'm erring on the side of including it.

Yours Tony.


signature.asc
Description: PGP signature
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-12 Thread gordon chung 


On 12/04/17 02:47 AM, Tony Breeds wrote:
> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
> - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing 
> and
>   why.  Note doing this will amost certainly reduce the testing coverage you
>   have in the gate.
> - A project is in list 2 that would like to opt *IN* to tagging/EOLing

i imagine you can EOL python-aodhclient and ceilometermiddleware. thanks 
Tony!

cheers,

-- 
gord
__
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][stable][ptls] Tagging mitaka as EOL

2017-04-12 Thread Andreas Jaeger 
Please add openstack-manuals to the list for EOL,

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][stable][ptls] Tagging mitaka as EOL

2017-04-12 Thread Alex Schultz 
On Wed, Apr 12, 2017 at 12:47 AM, Tony Breeds  wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
>
> I'm proposing to EOL all projects that meet one or more of the following
> criteria:
>
> - The project is openstack-dev/devstack, openstack-dev/grenade or
>   openstack/requirements
> - The project has the 'check-requirements' job listed as a template in
>   project-config:zuul/layout.yaml
> - The project gates with either devstack or grenade jobs
> - The project is listed in governance:reference/projects.yaml and is tagged
>   with 'stable:follows-policy'.
>
> Some statistics:
> All Repos  : 1584 (covered in zuul/layout.yaml)
> Checked Repos  :  416 (match one or more of the above 
> criteria)
> Repos with mitaka branches :  409
> EOL Repos  :  199 (repos that match the criteria *and* 
> have
>a mitaka branch) [1]
> NOT EOL Repos  :  210 (repos with a mitaka branch but
>otherwise do not match) [2]
> DSVM Repos (staying)   :   68 (repos that use dsvm but don't have
>mitaka branches)
> Tagged Repos   :0
> Open Reviews   :  159 (reviews to close)
>
> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
> - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing 
> and
>   why.  Note doing this will amost certainly reduce the testing coverage you
>   have in the gate.
> - A project is in list 2 that would like to opt *IN* to tagging/EOLing
>

Please EOL the Puppet OpenStack projects that have the stable/mitaka branch.

Thanks,
-Alex

> Any projects that will be EOL'd will need all open reviews abandoned before it
> can be processed.  I'm very happy to do this, or if I don't have permissios to
> do it ask a gerrit admin to do it.
>
> Yours Tony.
>
> [1] 
> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L1
> [2] 
> https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L209
>
> __
> 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][stable][ptls] Tagging mitaka as EOL

2017-04-12 Thread Tony Breeds 
Hi all,
I'm late in sending this announement, but I'm glad to see several projects
have already requested EOL releases to make it trivial and obvious where to
apply the tag.

I'm proposing to EOL all projects that meet one or more of the following
criteria:

- The project is openstack-dev/devstack, openstack-dev/grenade or
  openstack/requirements
- The project has the 'check-requirements' job listed as a template in
  project-config:zuul/layout.yaml
- The project gates with either devstack or grenade jobs
- The project is listed in governance:reference/projects.yaml and is tagged
  with 'stable:follows-policy'.

Some statistics:
All Repos  : 1584 (covered in zuul/layout.yaml)
Checked Repos  :  416 (match one or more of the above criteria)
Repos with mitaka branches :  409
EOL Repos  :  199 (repos that match the criteria *and* have
   a mitaka branch) [1]
NOT EOL Repos  :  210 (repos with a mitaka branch but
   otherwise do not match) [2]
DSVM Repos (staying)   :   68 (repos that use dsvm but don't have
   mitaka branches)
Tagged Repos   :0
Open Reviews   :  159 (reviews to close)

Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
- A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing and
  why.  Note doing this will amost certainly reduce the testing coverage you
  have in the gate.
- A project is in list 2 that would like to opt *IN* to tagging/EOLing

Any projects that will be EOL'd will need all open reviews abandoned before it
can be processed.  I'm very happy to do this, or if I don't have permissios to
do it ask a gerrit admin to do it.

Yours Tony.

[1] 
https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L1
[2] 
https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L209


signature.asc
Description: PGP signature
__
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