Tuesday Jul 10, 2007

Put your patch upstream

Today is a Sun patch day for us engineers working on Java Desktop System. We invited gnome hackers to join us, review our patches, and push the less controversial ones upstream.

We keep trying to put our patches upstream, i.e. put them back to the community code base. Putting patches upstream not only contributes to community, but also helps us lower our maintenance cost.

Take Mozilla for example, when we worked on Mozilla 1.7, because of the tight schedule and some other reason, we held many patches ourselves, especially on accessibility module. The good thing was, we made Sun Mozilla 1.7 much more accessible. While the bad thing is when community code base move forward, we had to spend much time to update our own patches to make them comply with the latest code. Sometimes it was painful, because there could be conflicts and regressions, since our patches were held locally and weren't tested with new code. And since those patches were not reviewed by community hackers, some of them also had potential problems. When Firefox comes out, we had to abandon many of the former patches.

Fortunately, we're working on HEAD now, all of our patches to Mozilla are put upstream (except some branding ones). When a new version of Firefox comes out, we can deliver our Solaris packages at the first time without wasting time on maintaining old patches.

Wish today a successful Sun Patch Day.

Thursday Jun 28, 2007

Mozilla CVS account

I have been granted with Mozilla CVS account. That means I have the check-in permission to Mozilla CVS repository now. And it's also a recognition for my work, I think.

It has been quite some time for me to get the account. I have been working on Mozilla, mainly on accessibility module, for more than one year. For some reason, patch for accessibility module do not need super-review before it can be checked in. That makes super-reviewers do not know much about our work. While to get a CVS account, super-reviewer's vouch is a compulsory requirement. So it is not easy. Thanks a lot to Robert, Aaron and Ginn for vouching me.

Accessibility is interesting, and it touches many other places in Mozilla code base, especially layout module. Learn more, have more fun.
 

Tuesday Dec 12, 2006

How to build l10n builds for mozilla applications

From mozilla web page, you can easily find out how to build a mozilla application(like Firefox and Thunderbird) with the default locale en-US. But it's not so easy to get how to build a l10n version. Here it is.

1. you have to check out  mozilla/tools/l10n/l10n.mk besides mozilla/client.mk.

$ cvs -d:pserver:anonymous-AT-cvs-mirror.mozilla-DOT-org:/cvsroot co mozilla/client.mk mozilla/tools/l10n/l10n.mk

2. do l10n-checkout before checking out the real code.

$ make -f client.mk l10n-checkout MOZ_CO_PROJECT=browser

3. create l10n files, replacing ab-CD with your locale, like zh-CN.

$ make -f tools/l10n/l10n.mk create-ab-CD MOZ_CO_PROJECT=browser

4. add this line into your .mozconfig file.

mk_add_options MOZ_CO_LOCALES=ab-CD

 

Then, do what you like as normal building.

$ make -f client.mk checkout
$ make -f client.mk build

 More detail information available here.

About

I'm a developer working on Solaris I/O framework. Formerly, I worked on Mozilla and GNOME projects.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today