Pavel's diary

... is exactly four years old now. It was #i5332#. This "disaster" was fixed very early.

The release of OpenOffice.org source code changed my work and also my life. Four years now. I'd like to thank my wife and also my son for their patience.

Office for Foreign Relations and Information (Czech foreign intelligence service) published set of selected documents and photos collected by intelligence service in communistic era. 4 minutes of TV prime time (daily days), several articles in today's newspapers.

Links: iDnes, Czech Radio, iHned, Živě.cz, Novinky.cz, Aktuálně.cz, Aktuálně.cz.

In one of the previous blog entries, I blogged about gsicheck and checking your translations easily.

Gregor Hartmann did even better thing - you can now download gsicheck for even more systems.

Very interesting news this week - Dell plans to use AMD Opterons in their servers, Apple's closing of Mac OS X for Intel, MacBook and Sun/Java/Open Source moves.

I like the first one, expected second one, welcome third and appreciate the last one.

Last week was hard. Working with people who expect report from you and do not apply/fix issues you reported is frustrating, especially as you need to do the work again and again and ... Finishing three big projects at the same time is also not optimal.

We are now working on 2.0.3 release, RC1 was already released. I have already uploaded GNU/Linux builds. Other systems will be soon (except GNU/Linux on AMD64 because of the motherboard in my build server).

Looks like I should do something pleasant on weekend. I already have an idea ;-)

Starting with SRC680_m167 (Build-1), I'll provide statically linked gsicheck binary executable for GNU/Linux with almost every build I'll upload. gsicheck.static will be located in the directory TranslationQA - e.g. here for SRC680_m167.

The usage of gsicheck.static is very simple - just run it with two arguments: "-c" and the GSI file. If it prints something, you have some bugs in your GSI file. Run it without arguments to get additional help.

Hope it will make it even easier for you to provide GSI files without mistakes.

If you are in our country and have some free time, visit the outlook-tower in Beroun (ten minutes away from Prague to the west, near the highway from Prague to Nürnberg). The outlook-tower is located in the center of the city surrounded by nice park with playground for children (my son enjoyed especially slide and swing).

And if you like to watch live animals, you have another motivation to visit the outlook-tower, because there is a park with three bears (as in bear, not beer).

I have started all builds of SRC680_m166 milestone. I have also added one new feature into my build system. build now supports generating HTML output with the possibility to keep the full build log in one file (thanks to Vladimir), so I use it and upload also HTML output file for your information (the HTML page references the text logs in the build that I do not pack, but it is usefull to get the general overview of the build and how long it takes).

HTML files will be uploaded to Build-x/build directory. First available example is here. It is a page from x86-64 build system, building 36 languages, all install sets in RPM and DEBs and language packs for all languages. The build took 8 hours (using two CPUs and four processes running in parallel) net time. It is not exact number, because I do build in two phases - I first build transex3 module so I can merge new translations in, and then the rest. It looks like it is next to impossible to build and deliver e.g. libxml2 module in one second ;-) But for modules above transex3 it looks realistic (I use ccache):

• instsetoo_native: 2 hour, 48 minutes (3 hours 38 minutes on x86)
• helpcontent2: 1 hour, 23 minutes (1 hour 42 minutes on x86)
• binfilter: 33 minutes (1 hour 8 minutes on x86)
• svx: 22 minutes (34 minutes on x86)
• sw: 21 minutes (46 minutes on x86)
• sc: 17 minutes (38 minutes on x86)
• sd: 11 minutes (27 minutes on x86)

Now you understand why we all love to build helpcontent2 :-)

We are getting closer to 2.0.3 but we still have so many issues with target 2.0.3... Many of them are expected (pending GSI files merge), but there are lot of issues that are simply "forgotten" by their owners. It would be a shame to not properly process e.g. PATCHes... Please try to do your best for 2.0.3.

May 1 is always special day. People kiss themselves bellow trees etc.

But do you remember that four years ago, the OpenOffice.org project released OpenOffice.org version 1.0? Do you want to touch the history? Browse the dev@marketing mailing list.