Open Stack

Hello,

On 07/29/2015 09:38 PM, Elizabeth K. Joseph wrote:
> On Wed, Jul 29, 2015 at 2:48 AM, Yanis Guenane <yguenane at redhat.com> wrote:
>> Hello,
>>
>> This morning due to a mis-configuration in one of my tool a branch has been pushed to 4 projects it shouldn't have.
>>
>> Branch name:
>>
>>   * msync_automatic_update
> No problem. I'll also include the sha tip of each below in case there
> are any issues and we need to work to revert any deletions.
>
>> Projects Impacted :
>>
>>   * openstack/puppet-ceilometer
> Done.
>
> 5c66f6b4cd148af397755e353d0d7811a37d7eed

Not sure this has been done correctly as I still can see the branch
https://github.com/openstack/puppet-ceilometer/tree/msync_automatic_update

>
>>   * openstack/puppet-cinder
> Done.
>
> 84141dfab6643d6362167833a778bed49c95cee7

Branch removed.

>
>>   * openstack/puppet-designate
> Done.
>
> af714071d293ac450b22f4deeb2443a25d997ada

Branch removed.

>
>>   * openstack/puppet-glance
> Done.
>
> 953ae932167f709b9dfb126f1cc1acf7adb6eaf4

Branch removed.

Thanks a lot Elizabeth for taking care of that.

>
> And I'd echo Andreas' recommendation that a puppet-manager-release
> team be added to the openstack-infra/project-config repo in the
> gerrit/acls/openstack/puppet-modules.config file (see other ACLs for
> examples) if the team wishes to reduce the risk of this happening by
> having a designated release team rather than all cores able to add
> branches.
>

--
Yanis Guenane