I'm going to float some ideas that may be controversial here first. If
there's agreement, we can move details to the bug.
On Wed, Jun 1, 2016 at 10:01 AM, Jonathan Griffin <
jgri...@mozilla.com>
wrote:
I'll actually propose NOT doing the tarball archive (to lighten the process
even further). The tarballs we archived for BZR & CVS were to preserve
"last state in this version control system" (not "last state on this
host"). They are a safety net for information loss due to lost backups or
improper migration.
For all-but-one repo on
git.mozilla.org, the repositories are moving to (or
already exist on) some other git server. At most we need some redirection,
IMO, but not a snapshot. (More on the exception below.)
The bulk of the 674 repos were for b2g, and were mirrors managed by
vcs-sync. There were two reasons for the repositories to be on
git.mozilla.org:
a) to be publicly accessible by partners (primarily the first partner, and
no longer required)
b) "inside the firewall" cache for releng build machinery (no longer
operational)
There were no developers committing directly to
git.mozilla.org for b2g.
I.e. all the repos are already hosted elsewhere, either:
1) on
github.com/mozilla-b2g (for repositories with "Mozilla contributions
to b2g")
2) on the authoritative server for that repo (e.g. android stuff
unmodified by us)
In practical terms, for community folks continuing to work on FxOS or b2g,
simply updating the manifests in
github.com/mozilla-b2g/b2g-manifests to
ensure there are no references to
git.mozilla.org will keep their builds
from being broken. (That change could be made ASAP to minimize any
surprises later.) If we wanted, we could also publish the vcs-sync mapping,
if folks want that detail.
The one exception is releases/gecko.git - that is/was the partner facing
repo of gecko converted from hg to git. That repo is no longer being
updated, and only exists on
git.mozilla.org. I think there is developer
value to having that available as a git repository (for debugging, etc.). I
believe that is best served by making a read only upload to
github.com/mozilla-b2g, where the manifests can refer to it. Archiving that
repo (since it's end of life) is also reasonable. One tarball is much less
than 674 tarballs ;)
--Hal