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 > <https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt> > > On Thu, Jun 29, 2017 at 10:57 PM, Jeremy Stanley <fu...@yuggoth.org > <mailto:fu...@yuggoth.org>> 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://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <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