917173 - In partner facing http://git.mozilla.org/?p=releases/gecko.git delete obsolete "aurora" branch

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

In http://git.mozilla.org/?p=releases/gecko.git, please delete the obsolete "aurora" branch. This hg->git replication of mozilla-aurora was part of the initial scramble in pre-v1.0 setup. It was quickly abandoned as B2G rode the trains to mozilla-b2g18, and has not been used by any partners since then (at least 5 months).
 
Now that we are getting ready for v1.2, we should delete this "aurora" branch from http://git.mozilla.org/?p=releases/gecko.git to avoid confusion with partners. Per agreement with external partners, they are happy to be using "v1.2" branch within http://git.mozilla.org/?p=releases/gecko.git and https://git.mozilla.org/?p=releases/gaia.git, once created as part of the migration work, because using "v1.2" will eliminate need for partner coordinated changes as Mozilla B2G rides the trains.


Note: this deletion is *only* to happen in http://git.mozilla.org/?p=releases/gecko.git. Aurora is *NOT* to be deleted in hg! 
Note: The state of the different repos on github is confusing, and owned by multiple people, so ignoring for now as it does not block migration or partner handoffs. As we figure those other repos out with their owners, we'll file separate different bugs.

Comment 1

[Rail Aliiev [:rail]]

I have 2 questions here:

1) does it really block bug 913992?
2) should we resolve it as WONTFIX because deleting publicly available commits is a bad idea?

Comment 2

[Aki Sasaki (not active)]

M1: deleting this branch would reduce confusion, since it's not syncing.
However, it would violate the no-deletes fast-forward-only rules on the repo.

Do you have a preference or guidelines here?

Comment 3

[Michael Vines [:m1] [:evilmachines]]

We are not using this branch in any form, so deleting it would not not cause us any trouble at all.

I doubt anybody else is using it too.  Maybe delete it and see who squawks?

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to Michael Vines [:m1] [:evilmachines] from comment #3)
> We are not using this branch in any form, so deleting it would not not cause
> us any trouble at all.
> 
> I doubt anybody else is using it too.  Maybe delete it and see who squawks?

wfm.

Comment 5

[Aki Sasaki (not active)]

export GIT_SSH='/opt/vcs2vcs/mozharness/external_tools/git-ssh-wrapper.sh'
export GIT_SSH_KEY='~/.ssh/vcs-sync_rsa'
git push [e-mail]:releases/gecko :aurora
remote: error: denying ref deletion for refs/heads/aurora
To [e-mail]:releases/gecko
 ! [remote rejected] aurora (deletion prohibited)
error: failed to push some refs to '[e-mail]:releases/gecko'

We may need IT to help us here.
Hal, have you ever asked IT to delete a branch in gitolite?

Comment 6

[Hal Wine [:hwine] use NI!]

Yes, we'll need IT to disable the denyDeletes setting temporarily while the above is run, then re-enable.

The last time we did a deletion, we did not have that config option set, so did not need IT's help.

Comment 7

[Aki Sasaki (not active)]

Woot! done