GullFOSS
OpenOffice.org Engineering at Sun
 
 
 
 
More Flickr photos tagged with openoffice

Today's Page Hits: 1590

Locations of visitors to this page
« New: OpenOffice.org... | Main | Download system... »
Monday, 13 Oct 2008
Numbers about OOo 3.0 release
Thorsten Ziehm

At the 8th birthday of OpenOffice.org the release of OOo 3.0 is done. It was hard work for all teams especially at the end of this Major Release. In the release notes you can find what's new and cool in this major update. Thanks for all of you, who are working so hard to make this release possible today.

For all of you, who wants to have a deeper look into the release here are the statistics of OOo 3.0.

General numbers :

In ~590 CWSs more than ~2850 issues were fixed and integrated into the code line for OOo 3.0. These are the numbers for OOo 3.0 code line only. In between there were also the last fixes for OOo 2.4 and all issues from OOo 2.4.1 integrated. This leads to more than 3100 issues are in since the split of OOo 2.x and OOo 3.0 (DEV300m...) code lines. That's a mass and nearly double the numbers for the last feature release OOo 2.4.

CWS numbers :

Chart about numbers of integrated CWS in OOo 3.0 final

As you can see in the graphs most of the CWS were integrated after Feature Freeze and also after Beta 1. This time was needed to polish the features, fix the critical bugs which were reported by beta testers and to clean up the install sets and setup to be as save as possible after the split to the 3 Layer Office.
77% of all CWS went through the full approval process of the Sun QA. 12% were approved by Release Engineering team, 5% by the Sun Development team and the contribution from the OOo community was round about at 6%.

Chart about numbers of integrated issues in OOo 3.0 final

The distribution on issues and user groups are a little bit different. 85% of the registered issues at a CWS were approved by Sun QA team, 7% by Sun RE team, 3% by Sun DEV team and 5% by the OOo community contribution.

Issue numbers / types :

Round about 350 issues marked as features or enhancements were integrated for OOo 3.0 until Feature Freeze. Some of them were late, some came too late and some had to be integrated after Beta 2. Which components got most of it, can be seen in the next graph.

Chart about integrated features in OOo 3.0 per component

More than 1700 issues which are marked as bugs were fixed.

Chart about integrated bug fixes in OOo 3.0 per component

Exactly 300 issues which marked as patch (most code contribution by community members) were fixed and integrated also in OOo 3.0.

Chart about integrated patches in OOo 3.0 per component

The rest of 240 issues are marked as tasks. (This is a very critical mass! Nobody knows why some developers mark features/enhancements and bug fixes as this type of issue.)

These are nearly 2600 issues which are tracked in the IssueTracker on OOo. The rest are Sun internal issue like stacktrace issues (issues generated from the crash reports by OOo users).

Summary :

With OOo 3.0 the native Aqua platform for MAC was introduced. This leads to a high number of features and issues in GSL (General System Layer) project. The general feedback for the MAC platform on OOo is very positive. There are some general issues still open to get the same quality as on the other platforms. But as many users reported it's the best version they ever had on MAC.

OOo 3.0 was a Major Release and in it many general restructuring and refactoring was started. Also from now on the default file format is based on ODF 1.2 (the standard will be approved soon) instead of ODF 1.1 in OOo 2.x. All these changes could be done in a major step only, because of possible incompatibilities to the the 2.x code line.

This major release was a challenge for all release driver on OOo. Also the OOo teams for QA and L10N had many new things to organize, which didn't exists on OOo 2.x code line or wasn't a problem for that updates. Thanks to all the teams for their hard work.

In general the quality of OOo 3.0 is very high. In comparison with OOo 2.0 final this version is much much better. But there are still some issues open and I think there will come up more critical issues since today, when OOo 3.0 will be used in general work flow on many systems. These issues will be addressed in OOo 3.0.1, which should came out end of November/begin of December '08.

Give OOo 3.0 a try. As I see many users do it now. The side seems to be down by the high download rate. So stay tuned and download the version for your daily work soon!

tags:

Posted by Thorsten Ziehm on 13 Oct 2008  |  PermaLink |  Bookmark to Delicious To Delicious |  Digg this Digg this  |  Comments[6]

Comments

Travis said:

Ugh. The Snap previews are horrible. And the "disable" options simply don't work (search the web and find lots of people complain about the same thing). It's like a telemarker calling me every time I hover over a link. I ask them to stop... but the disable doesn't work. I've never met such an aggressive telemarker. It's unclear to me why you'd want to punish people who are reading your blog and thinking of following the links. Consider me punished.

Posted by Travis on October 13, 2008 at 10:07 PM CEST #

mattia said:

Starting up is a little bit slow and Impress' effects are unusable on MacOSX becouse they are sluggish.
I'm hoping for 3.1 to be the "definitive" porting to Mac.

Posted by mattia on October 13, 2008 at 11:58 PM CEST #

Ganesha Bhaskara said:

Could you please shed some light on the release date of staroffice 9.

-Ganesha

PS: Travis ...... adblock+noscript

Posted by Ganesha Bhaskara on October 14, 2008 at 04:46 AM CEST #

Thorsten Ziehm said:

StarOffice 9 will be live end of October.

Posted by Thorsten Ziehm on October 14, 2008 at 08:54 AM CEST #

Someone said:

<citation>
The rest of 240 issues are marked as tasks. (This is a very critical mass! Nobody knows why some developers mark features/enhancements and bug fixes as this type of issue.)
</citation>

Because some things just have to be done (e.g. in preparation of future work), without being a DEFECT (nothing is broken), or an ENHANCEMENT or FEATURE (nothing visible to the user will change). In those cases, TASK is the only appropriate issue type.

Given that your statistics cover the time since the 2.0 release (at least this is how I understood it), a number of 240 TASKs is not really *that* high, I'd say.

Posted by 192.18.1.36 on October 15, 2008 at 09:25 AM CEST #

Thorsten Ziehm said:

This statistics are from the last feature release (OOo 2.4). It isn't since OOo 2.0 release.
Regards, Thorsten

Posted by Thorsten Ziehm on October 15, 2008 at 10:12 AM CEST #

Post a Comment:
Comments are closed for this entry.
« New: OpenOffice.org... | Main | Download system... » GullFOSS