> On Feb 15, 2019, at 2:34 PM, Bryan Call <bc...@apache.org> wrote:
> 
> Thank you for being able to resolve most of the branches.   Leif had a hourly 
> backup, so I was able to restore 7.1.x and 8.0.x to its original state.


Also, just as an FYI, but these hourly backups (btrfs snapshots actually) are 
done automatically. We snapshot the disk every hour (keeping 24h), and once a 
day (keeping 7 days), and once a week (keeping 3 months).  This is done as part 
of the Github mirroring that I setup for our CI (to avoid clobbering Github 
with git clone / git fetch requests and get us banned).

So, even though this shouldn’t happen (often … :) we hopefully have pretty good 
backups available for emergencies like this.

I’m thinking we should ask the ASF Infra ops team to protect the release 
branches at least. Protecting a branch means that it can not be deleted, or 
force pushed to. We already have this on the master branch, and in addition, we 
require PRs to push to to  master. We should obviously not require PRs to push 
to the release branches though, and it’s an optional setting.

Cheers,

— leif

P.s
I’m thinking we should protect these:

  remotes/origin/2.0.x
  remotes/origin/3.0.x
  remotes/origin/3.2.x
  remotes/origin/3.3.x
  remotes/origin/4.0.x
  remotes/origin/4.1.x
  remotes/origin/4.2.1.x
  remotes/origin/4.2.x
  remotes/origin/5.0.x
  remotes/origin/5.1.x
  remotes/origin/5.2.x
  remotes/origin/5.3.x
  remotes/origin/6.0.x
  remotes/origin/6.1.x
  remotes/origin/6.2.x
  remotes/origin/7.0.x
  remotes/origin/7.1.x
  remotes/origin/8.0.x
  remotes/origin/8.1.x


Reply via email to