Re: [OpenStack-Infra] Zuul feature/zuulv3 branch to be rewound
Darragh Bailey writes: >> The abandon/restore steps are required by Gerrit in order to delete the >> branch. We could force-push the branch tip, but this is the procedure >> we have asked and would ask any other project to use in a similar >> situation, in order to reduce the risk of error. > > Can you elaborate more on how this reduces risk/errors? Curious in case we > run into a similar scenario in the future. Deleting/creating branches entails granting fewer permissions in Gerrit, so there is less opportunity to accidentally commit an error such as pushing to the wrong branch, or accidentally pushing local tags, etc. Creating a branch through the Gerrit web UI is also a very deliberate step, arguably easier to verify than a push. It's not a lot of extra safety. Just some. -Jim ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Zuul feature/zuulv3 branch to be rewound
On 21 Sep 2017 6:38 pm, "James E. Blair" wrote: Hi, Snipped 1) Abandon all open changes on feature/zuulv3. 2) Delete the feature/zuulv3 branch. 3) Re-create the feature/zuulv3 branch at the commit before the Sem-Ver change: 027ba992595d23e920a9cf84f67c87959a4b2a13. 4) Restore all the changes abandoned in step 1. The abandon/restore steps are required by Gerrit in order to delete the branch. We could force-push the branch tip, but this is the procedure we have asked and would ask any other project to use in a similar situation, in order to reduce the risk of error. Can you elaborate more on how this reduces risk/errors? Curious in case we run into a similar scenario in the future. -- Darragh Bailey "Nothing is foolproof to a sufficiently talented fool" - unknown ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
