Pavel's diary

Current status of bugs with target 2.0: 45 issues.

I haven't reach my goal to limit the number of issues for 2.0 to 40 (thanks anyone who helped!), but 45 is also good number! We still have a lot of work - 25 of them are still in NEW status so they was not evaluated at all, 7 issues of P2 importance. -----

The current status of issues with target 2.0 is: 51 issues (see IZ).

Current temperature here (Prague, Ruzyně airport):

-----

Current status of bugs with target 2.0: 61 issues.

32 of them are in state NEW. This means that bugs are new, confirmed but the person to whom bug is assigned haven't started to work on it. This means the bug is either not that important or the person simply forget to set the status correctly. Please update your issues!

6 of them are assigned to me to (planned) pj32 and thus they are in STARTED state already.

I have a goal to make the number below 40 in 24 hours. Can you help us to reach this goal and make OpenOffice.org 2.0 release happen earlier? -----

This poll is a protest against people who do not follow our project mailing list guidelines and do not listen to people who are pointing to them.

Objective: find an e-mail from someone else in the mailing list archives of our project that breaks most of the advises in the guidelines.

Prize: cold Czech beer/coke (depends on your preference) on the beach at OOoCon 2005 in Koper, Slovenia!

Deadline: this Friday, 23:59:59 UTC. -----

I have decided to stabilize my build system in the preparation for 2.0 release.

I especially do not plan to add new languages *before* 2.0 is released. I'll add new languages once 2.0 is released. Please contact me after 2.0 release if you want to add your language into my build system. -----

I have decided to update my build server's gtk+ and company. I thought it will be easy. Hmm, it was not. I had to install/update several tools.

I have decided to not go the straight way of installing newer SuSE Linux (I still use 9.0 on my build server because of backward compatibility of produced builds). So I installed new pieces, namely: glib-2.4.8, atk-1.8.0, pango-1.4.1, gtk+-2.4.14, libIDL-0.8.3, ORBit2-2.10.2, GConf-2.7.1, libbonobo-2.6.2, gnome-mime-data-2.4.1 and gnome-vfs-2.7.1.

Yes, all of them. Hmm.

I used this script to make it reproducible for other users of my build system.

The first build with this stuff will be Build-3 of SRC680_m121 (gnomevfs will be enabled in it again). Of course only if the build is successful ;-) -----

The milestone SRC680_m121 is now ready. Child Workspaces integrated: dba20v2, impress65, localedata5, pleasereadme, swqbf38 and swqbf39.

My builds were OK on both GNU/Linux (gcc-3.4.1) and Microsoft Windows. MacOS X is still building.

Child workspace pleasereadme integrated changes in README file, so please update your translations. -----

Czech translation team has finished help content translation and the QA phase begins. We have used the Online Help Link Creater and we have created a statistics of the work at our project pages.

This tool allows us to manage distributed QA process effectively. -----

Our team of translators led by Adam Rambousek finished the translation of OpenOffice.org 2.0 PO files! 57600 strings are finally translated:



Thanks everyone who made this possible. This version will be the largest piece of software released in 2005! -----

Final deadline for providing updated GSI files for OpenOffice.org is 2005/08/05. -----

The milestone SRC680_m120 is ready.

Public child workspaces integrated:dummywebwizard, fwk18, hsqldb6, leansofficesh, mhu09, mtl10n03 and nativefixer16.

Other child workspaces integrated: introbitmapfix (only the Sun StarOffice splashscreen bitmap changed) and jl21bean (changes in modules bean and vcl). -----

One of the problems we still see in our cws development model is wrong or completely missing description of child workspaces. People reading cws-announce mailing-list will actually read the description of your child workspace, so please keep it informative and fill it at all!

Very good example is kendy's child workspace iconswitching1. It contains full description of the work that will be in his child workspace. It can even attract people to test it and thus help kendy with its debugging!

Not that bad (but could be better) example is child workspace swqbf39. Its description references issues being fixed ("fixes for issue i51733 and i52225") in this cws. This is redundant information, because these issues will surely be assigned to this child workspace and you still do not know what this cws is all about and have to open IZ and read the summary of both issues. But it at least contains some description.

The very bad example is hsqldb6. It is a really small child workspace (already integrated, BTW) and its description is empty. I understand that it was quick cws, but it should have non-empty description!

All child workspaces were chosen randomly. The only exception being kendy's iconswitching1 because I took inspiration from its description (but I believe there are other good examples as well). I know that the chosen child workspaces are not very good candidates, because new feature developed in iconswitching1 surely needs better description than small bugfix cws hsqldb6, but think about the principles instead of details... -----

The milestone SRC680_m119 is ready for your work.

Integrated child workspaces: cmcfixes10, cmcfixes11, doubleprop, impress64, jl23, l10ntoolingfixer, mhu08, swnum03, sysui09 and tl13. -----

On Saturday, our family went to castle Karlštejn. This castle is about 15 minutes (by car) away from Rudná, where we live. Really nice weather combined with really old gothic castle from 14th century.

Even my one year old son enjoyed the trip. -----

The milestone SRC680_m118 is now ready. It integrated many child workspaces: dba20v1, dvoqbfix4, fs01, fs02, hsqldb5, impress51, impress61, impress63, linuxppc04, mh19104, nativefixer14, pl06, so8w98cjk, thb08 and vgbitmapcleanup.

Please test it very carefully. Many bitmaps were removed during the cleanup so have a look at bitmaps and their usage. Two known issues are removed images in module pyuno, directory doc and module extras (hjs mentioned them in EIS).

No changes in exported strings, so no need to updated POT files.

Update: See #i51409# for build breaker in module hsqldb and #i52061# for another build issue. -----

The milestone SRC680_m117 is now ready for your work. Child Workspaces integrated: ause030, fpicker4, fwk16, mav18, mtl10n, os65, sj21, stlportcleaner and swqbf37. -----

SRC680_m116 has been built by Hamburg RE. Child Workspaces integrated: ab18, dba20blocker, fwk14, impress62, jl22, lostformating, nativefixer12, pj30, sb32, sb33, sch11 and swqbf34. -----

The milestone SRC680_m115 is now ready. It includes child workspaces lostgrouping, mmeeks09, qwizardsbfooo20, sch10 and vcl41.

POT files are updated. -----

No!, thanks. -----

The milestone SRC680_m114 is ready. Integrated child workspaces: expconbin, macosx09, memory01, pl04, pl05, vq19 and wizopendb. -----