-
Notifications
You must be signed in to change notification settings - Fork 329
FAQ
Will the firefox-android repository on GitHub be archived on March 18th, 2024?
No. The main branch will be closed but the repository will still be open to accept contributions on the releases_v124 and the upcoming releases_v125 branches. Pull requests specific to Firefox for Android 124 and 125 will still be accepted against these branches.
The firefox-android repository on GitHub will be archived on May 14th, 2024, after Firefox for Android 126 gets generally available.
Yes. Even though the canonical repository will be on Mercurial, we do support Git as a VCS tool as the tier-1 VCS. Mozilla is planning to deprecate the Mercurial support to move to a full Git workflow. You can follow these instructions starting today.
No. Starting March 18th, 2024, contributions to Firefox for Android 126 and beyond will be only accepted through Bugzilla and Phabricator, our code review tool. Firefox for Android has used Bugzilla as an issue tracker for more than a year. You can log in to Phabricator with your existing Bugzilla account.
Yes, you can fork gecko-dev. It’s Mozilla’s official Git mirror of mozilla-central on hg.mozilla.org. It’s read-only so contributions will only be accepted through Phabricator. Note that this repository will be deprecated in the future as part of the migration of Firefox Development from Mercurial to Git.
After the migration is done, here are the steps to follow to convert a Github Pull Requests to Phabricator revision:
-
cd mozilla-unified# Go to the directory of your local clone. curl -L https://github.com/mozilla-mobile/firefox-android/pull/$PULL_REQUEST_NUMBER.patch > your.patch # Replace $PULL_REQUEST_NUMBER- Depending on whether you use Mercurial or Git:
hg import --prefix mobile/android your.patchgit am --directory=mobile/android your.patch
moz-phab submit
Yes. Just like Firefox Desktop, we will provide a fast build mode we call Artifact Builds.