Friday, 11 Apr 2008
Friday, 11 Apr 2008
This release was the last feature release on code line OOo 2.x. The development and all other teams gave speed to integrate more features than in the last feature releases. Which features are integrated can be found in the release notes, in Andrew Ziem's OOoNinja blog with many pictures or in my more technical orientated feature list.
As I wrote in other blogs ago, I am a fan of numbers and statistics. Therefore here are more information about this release.
Issue numbers :
In 315 CWSs round about 1700 issues were integrated for this release. These are the numbers for this release only. 244 features and enhancements, 240 patches and 992 fixes for detects and tasks are integrated. Other issues are for example crash reporter issues, which currently can be tracked inside Sun only. In sum more CWS are integrated and can be queried in EIS. Because all CWS after the branch of OOF (OOo2.3) and all CWS from OOG (OOo2.3.1) are copied also in this trunk.
CWS numbers :
As written above 315 CWS are integrated into code line for OOo 2.4. Also all CWS for OOo 2.3.1 and some CWS which are integrated after the split of branch of OOo 2.3. are integrated. In sum round about 400 CWS with 1900 issues are integrated.
70% of all CWS go through the approval process of the Sun QA. 12% are go through the Release Engineering team, 8% are approved by the Sun Development team and the contribution from the OOo community is round about at 9%.
The highlights in this diagram are m238 ( Feature Freeze) with 50 CWS integrations and m4 ( Code Freeze) with 38 integrations.
The highlights of Feature Freeze and Code Freeze are also seen in this diagram. Round about 290 issues are integrated in m238 and nearly 250 in m4.
The distribution on issues and user groups are a little bit different. 80% of the registered issues were approved by Sun QA team, 12% by Sun RE team, 4% by Sun DEV team and 5 % by the OOo community contribution.
Crash reports :
The crash reporter tooling in OOo and also in StarOffice is a good indicator, if we are on the right way with stability of OOo/SO. The most critical issues were identified. 31 issues were fixed for this release. ~55.000 crash reports were send to our internal data base for these sometime difficult to reproducible crashes. The incoming crash reports show that the general stability increased over the last releases. There are still crashes and loops in OOo, but the number of critical issues decreased with our initiative to identify for each release the most reported issues from the last releases.
Summary :
Because of the vacation period around Christmas in the development and in the other teams the time for this release wasn't the full 6 month. But a mass of new features are integrated. So beside the bug fixing you can see some new features in that version.
The most concentration is now on OOo 3.0 and their Beta release end of this month. But the reports of some regressions in OOo 2.4 are coming in. So we will do a bug fix release on 2.x code line beside the other releases. The time line isn't clear now, but take frequently a look at the release map for OOo 2.4.1.
Stay tuned, have fun with OOo 2.4 and if you are interested in new features on OOo 3.0, take a look at my last blog here on GullFoss.
tags: