While it sounds like I should really switch to a bookmark-based Mercurial workflow for my Gecko development, I figured that before I do that, I should document how I currently use patch queues and Bitbucket.

Starting work on a new bug

After creating a new bug in Bugzilla, I do the following:

1. Create a new mozilla-central-mq-BUGNUMBER repo on Bitbucket using the web interface and put https://bugzilla.mozilla.org/show_bug.cgi?id=BUGNUMBER as the Website in the repository settings.
2. Create a new patch queue: hg qqueue -c BUGNUMBER
3. Initialize the patch queue: hg init --mq
4. Make some changes.
5. Create a new patch: hg qnew -Ue bugBUGNUMBER.patch
6. Commit the patch to the mq repo: hg commit --mq -m "Initial version"
7. Push the mq repo to Bitbucket: hg push --mq ssh://hg@bitbucket.org/fmarier/mozilla-central-mq-BUGNUMBER

8. Make the above URL the default for pull/push by putting this in .hg/patches-BUGNUMBER/.hg/hgrc:

   [paths]
   default = https://bitbucket.org/fmarier/mozilla-central-mq-BUGNUMBER
   default-push = ssh://hg@bitbucket.org/fmarier/mozilla-central-mq-BUGNUMBER
   

Working on a bug

I like to preserve the history of the work I did on a patch. So once I've got some meaningful changes to commit to my patch queue repo, I do the following:

1. Add the changes to the current patch: hg qref
2. Check that everything looks fine: hg diff --mq
3. Commit the changes to the mq repo: hg commit --mq
4. Push the changes to Bitbucket: hg push --mq

Switching between bugs

Since I have one patch queue per bug, I can easily work on more than one bug at a time without having to clone the repository again and work from a different directory.

Here's how I switch between patch queues:

1. Unapply the current queue's patches: hg qpop -a
2. Switch to the new queue: hg qqueue BUGNUMBER
3. Apply all of the new queue's patches: hg qpush -a

Rebasing a patch queue

To rebase my patch onto the latest mozilla-central tip, I do the following:

1. Unapply patches using hg qpop -a
2. Update the branch: hg pull -u
3. Reapply the first patch: hg qpush and resolve any conflicts
4. Update the patch file in the queue: hg qref
5. Repeat steps 3 and 4 for each patch.
6. Commit the changes: hg commit --mq -m "Rebase patch"

Credits

Thanks to Thinker Lee for telling me about qqueue and Chris Pearce for explaining to me how he uses mq repos on Bitbucket.

Of course, feel free to leave a comment if I missed anything useful or if there's a easier way to do any of the above.

Firefox Hello is a new beta feature in Firefox 34 which give users the ability to do plugin-free video-conferencing without leaving the browser (using WebRTC technology).

If you cannot get it to work after adding the Hello button to the toolbar, this post may help.

Preferences to check

There are a few preferences to check in about:config:

• media.peerconnection.enabled should be true
• network.websocket.enabled should be true
• loop.enabled should be true
• loop.throttled should be false

NoScript

If you use the popular NoScript add-on, you will need to whitelist the following hosts:

• about:loopconversation
• hello.firefox.com
• loop.services.mozilla.com
• opentok.com
• tokbox.com

RequestPolicy

If you use the less popular but equally annoying RequestPolicy add-on, then you will need to whitelist the following origin to destination mappings:

• about:loopconversation -> opentok.com
• about:loopconversation -> tokbox.com
• firefox.com -> mozilla.com
• firefox.com -> opentok.com
• firefox.com -> tokbox.com

If you find a more restrictive policy that works, please leave a comment!