The unified Firefox repo has now been moved out of experimental status and is available at https://hg.mozilla.org/mozilla-unified <https://hg.mozilla.org/firefox>. The repository is read-only and contains most of the commits from the main Firefox repos in chronological order.
Pre-generated bundles for the repo are available on our CDN ( https://hg.cdn.mozilla.net/) and are 300MB smaller than mozilla-central. When converting to the unified repo, I recommend using the one-line bootstrapper to clone the repo: $ wget https://hg.mozilla.org/mozilla-central/raw-file/tip/python/mozboot/bin/bootstrap.py $ python2.7 bootstrap.py (The bootstrapper now runs the [recently rewritten] Mercurial config wizard and offers to clone the repo using optimal settings. But it only offers to clone if you aren't in a checkout, so you need to run the bootstrapper standalone - not via `mach bootstrap`.) More docs for working with the unified repo are available at https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/unifiedrepo.html . The experimental URL still works (but is a slightly different repo). If you have already cloned/pulled from https://hg.mozilla.org/experimental/firefox-unified, you can simply update your .hg/hgrc's [paths] to point to https://hg.mozilla.org/mozilla-unified <https://hg.mozilla.org/firefox>. (Note: https://hg.mozilla.org/firefox was the initial planned location for the unified repo and some of you may have started using it. There was a last minute change of name to "mozilla-unified." https://hg.mozilla.org/firefox is no longer updating and will eventually be deleted.) On Fri, Apr 15, 2016 at 1:22 AM, Gregory Szorc <g...@mozilla.com> wrote: > I'm pleased to announce the immediate availability of some *experimental* > read-only Mercurial repositories containing the combined, useful history of > the various Firefox repositories, all in chronological order and stored in > a more efficient format that is faster to clone and pull from and results > in faster client operations. > > The repositories can be found at https://hg.mozilla.org/experimental. The > repository you likely want to clone is > https://hg.mozilla.org/experimental/firefox-unified. A visualization > showing the chronological history of the repo can be seen at > https://hg.mozilla.org/experimental/firefox-unified/graph. > > The primary goal of these repositories is to provide developers (and > eventually automation) with more efficient interaction with the Firefox > source repositories. There are several secondary and side-benefits, > including improving the scalability of Try and MozReview's repositories. > > More documentation about these repos is available at [1]. tl;dr > > * The repositories contain all the commits from the Firefox repositories > you use everyday (central, inbound, fx-team, aurora, beta, esr, etc). > * The repositories do not contain all the *_RELBRANCH branches (which > basically have no value to the average developer). > * Thes unified repositories are ~300MB *smaller* than mozilla-central > despite containing ~28,000 more commits. This was achieved through light > magic. > * Mercurial bookmarks are used to track the heads of the various Firefox > repos. > * The pushlog data is derived from the first known push of a changeset, so > it should match what's on e.g. central, inbound, etc. > * Sadly, git-cinnabar won't be able to talk to these repos just yet due to > git-cinnabar not supporting some modern Mercurial features. A GitHub issue > is on file at [2]. > > If you use the "firefoxtree" extension to manage a unified repository > today, you should consider switching to one of these new unified > repositories instead: it should be faster and easier to reason about. > > The repositories have the "experimental" label attached so we can reserve > the right to make changes without people complaining too loudly about > backwards compatibility. (But I wouldn't worry too much about stability - > I'm committed to keeping these running and improving them.) The goal is to > flush out issues with these repositories then remove the "experimental" > label. After that, we can have automation start consuming these > repositories. After that, we can perhaps start thinking about consolidating > around a single, canonical repository, including pushing. But that's a > topic for another day. > > I'm very anxious for feedback on these repositories. Please make noise in > dev-version-cont...@lists.mozilla.org, #vcs, the "Developer Services: > Mercurial: hg.mozilla.org" bug component, or in bug 1108729. > > [1] > https://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/unifiedrepo.html > [2] https://github.com/glandium/git-cinnabar/issues/64 > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
