Ben's Blog

During this time we will be deploying all of the changes listed on this page as well as two Talos bugs: bug 379233 and bug 458093

This will affect the following trees: Firefox (mozilla-central), Firefox3.1 (mozilla-1.9.1), Tracemonkey (tracemonkey), and Mobile (mobile-browser).

As a heads up please note that the Talos changes could affect numbers and will change the layout of the results on the Tinderbox Waterfall.

If there is any reason why we shouldn’t go ahead with this please e-mail release@mozilla.com.

If you are crashing after updating to the latest mozilla-1.9.1 nightly (20090218) try flipping javascript.options.jit.chrome to false – that should fix it. I’ve filed this as bug 479053 but flipping that pref should fix you up in the meantime.

During this time we will be deploying all of the changes listed on this page. Most notably, clobber support for all Mercurial based builds will be landed tomorrow. More on that soon from Chris AtLee soon.

This will affect all trees: Firefox (mozilla-central), Firefox3.1 (mozilla-1.9.1), Tracemonkey (tracemonkey), and Mobile (mobile-browser).

One of these requires a full Buildbot master restart – so expect some spurious burning. We’ll do our best to minimize it and get things green ASAP.

If there is any reason why we shouldn’t go ahead with this please e-mail release@mozilla.com.

Someone I know recently expressed interest in translating Firefox into her native language, Tagalog. Being a build guy, I decided to spare her the pain of getting everything setup and let her focus on the translation. Much to my dismay I discovered that the Create a New Localization page hasn’t been fully updated for Firefox 3.1 yet. By mashing together information on a couple of pages and a lot of help from #l10n I managed to get an environment up and running that allowed her to dive in.

Here’s how to do it. (Note: This has been tested on Mac and Windows. On Windows, this depends on MozillaBuild 1.3; on both it depends on Python setuptools.)

1. Install compare-locales

wget http://pypi.python.org/packages/2.5/c/compare-locales/compare_locales-0.6.1-py2.5.egg#md5=0b939a22d87427d80f5286dc5eb1eab2
easy_install compare_locales-0.6.1-py2.5.egg

2. Clone mozilla-1.9.1

hg clone http://hg.mozilla.org/releases/mozilla-1.9.1

3. Create the barebones localization

mkdir -p tl/browser/installer tl/browser/profile/chrome tl/browser/searchplugins tl/browser/updater tl/toolkit
cp mozilla-1.9.1/browser/locales/en-US/defines.inc tl/browser
cp mozilla-1.9.1/browser/locales/en-US/profile/chrome/userC* tl/browser/profile/chrome
cp mozilla-1.9.1/browser/locales/en-US/firefox-l10n.js tl/browser
cp mozilla-1.9.1/browser/locales/en-US/README.txt tl/browser
cp mozilla-1.9.1/browser/locales/en-US/searchplugins/list.txt tl/browser/searchplugins
cp mozilla-1.9.1/browser/locales/en-US/updater/updater.ini tl/browser/updater/updater.ini
cp mozilla-1.9.1/toolkit/locales/en-US/defines.inc tl/toolkit

4. Create a mozconfig file, setup your object directory

cd mozilla-1.9.1
echo “mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../fx-tl” > .mozconfig
echo “ac_add_options –with-l10n-base=../” >> .mozconfig
echo “ac_add_options –disable-compile-environment” >> .mozconfig
echo “ac_add_options –enable-application=browser” >> .mozconfig
make -f client.mk configure

5. Test merge-ab-CD and langpack-ab-CD targets

cd ../fx-tl
make -C browser/locales merge-tl LOCALE_MERGEDIR=`pwd`/../merge
make -C browser/locales langpack-tl LOCALE_MERGEDIR=`pwd`/../merge LANGPACK_FILE=`pwd`/../firefox-tl.xpi

If everything went well, you should be ready to translate now!

During this time we will be landing the patches listed on this page:

https://wiki.mozilla.org/ReleaseEngineering:BuildbotMasterChanges#Upcoming_changes

And as mentioned in Alice’s previous post we will be unthrottling the rest of the Talos machines. (http://groups.google.com/group/mozilla.dev.planning/msg/402afc2bfd2d65f2). This work is being tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=468680.

This will affect all trees: Firefox (mozilla-central), Firefox3.1 (mozilla-1.9.1), Tracemonkey (tracemonkey), and Mobile (mobile-browser).

One of these requires a full Buildbot master restart – so expect some spurious burning. We’ll do our best to minimize it and get things green ASAP.

If there is any reason why we shouldn’t go ahead with this please e-mail release@mozilla.com.

Both mozilla/tools/buildbotcustom and mozilla/tools/buildbot have now official moved to their new homes in Mercurial, http://hg.mozilla.org/build/buildbotcustom/ and http://hg.mozilla.org/build/buildbot/ respectively. The buildbotcustom CVS module will be deleted at the end of this week. We will be keeping the buildbot one for the time being because we have a Buildbot still using it, but all future work should be done against the Mercurial repository.

I thought I was going to avoid this meme altogether, but dave managed to tag me before it died out. Here goes:

The Rules

• Link to your original tagger(s) and list these rules in your post.
• Share seven facts about yourself in the post.
• Tag seven people at the end of your post by leaving their names and the links to their blogs.
• Let them know they’ve been tagged.

The Seven Things

1. I’ve been a geek my whole life. My earlier memory is playing Wheel Of Fortune and Family Feud on an i286 class machine with DOS 2.0 (maybe 3.0?) and a CGA display.
2. I’m a two time high school drop out.
3. Before getting my first “computer job” (see below) I worked various jobs including: pizza guy, grocery store stock clerk, ball packer, various assembly line jobs, and exactly one day as a dry cleaning machine operator.
4. I have never left North America.
5. In high school at one time or another I could have been rightly called the following: wigger, punk rocker, goth, metalhead, hippie, band geek, and computer geek (obvious). Sorry, no photographs are available.
6. I was a vegetarian for nearly 5 years until an overwhelming desire for red meat got the best of me.
7. I’m engaged to be married on a yet-to-be-determined date.

I think this thing has gone far enough, so I won’t be tagging anyone else.

The time has finally come for these two CVS modules to get a better home. Here’s what I’m proposing:

1. Early next week I will import these modules (with history) into http://hg.mozilla.org/build/buildbotcustom and http://hg.mozilla.org/build/buildbot.
2. On Friday, January 30th, 2009 I will delete mozilla/tools/buildbot and mozilla/tools/buildbotcustom from CVS and put in READMEs pointing to their new homes. I don’t believe there is any reason to keep them around once the new repositories are live. They will only serve to cause confusion.

Moving these will be a change for the better, I believe. It will let us import new versions of Buildbot without the hassle of CVS and in the case of buildbotcustom, let others work on it more easily.

If anyone has objections to this plan please respond to this mozilla.dev.builds post. If I don’t hear anything by Tuesday, January 27th I will proceed with this.

During this time we will be landing the patches listed on this page:

https://wiki.mozilla.org/ReleaseEngineering:BuildbotMasterChanges#Upcoming_changes

One of these requires a full Buildbot master restart – so expect some spurious burning. We’ll do our best to minimize it and get things green ASAP.

If there is any reason why we shouldn’t go ahead with this please e-mail release@mozilla.com.

bug 358845 pointed out that the ‘mZ’ we report for Codesighs tests is meaningless for Firefox. As such, we have stopped running it. This is just a quick note to let people know not to panic, it’s fine! The ‘Z’ number is still being reported and valid.