Removing the pbr branch should be fine - it was an exceptional thing to have that branch in the first place - pbr is consumed by releases only, and due to its place in the dependency graph is very very very hard to pin or cap.
-Rob On 25 June 2016 at 12:37, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Fri, Jun 24, 2016 at 04:36:03PM -0700, Sumit Naiksatam wrote: >> Hi Tony, Thanks for your response, and no worries! We can live with >> the kilo-eol tag, no need to try to delete it. And as you suggested, >> we can add a second eol tag when we actually EoL this branch. >> >> As regards reviving the deleted branches, would a bug have to be >> created somewhere to track this, or is this already on the radar of >> the infra team (thanks in advance if it already is)? > > No bug needed. I'll work with the infra team to re-create the branch. Just > as > a level set it wont be this weekend. > > 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