What is released with OOo 2.3!

This release was the first one, where the release schedule was 6 months. The last feature releases were released each 3 months. So there was more time to bring in bigger changes and features. Here are some numbers about the release.

Issue numbers :
In this release 370 CWS with nearly 2500 issues were integrated. There are 245 feature and enhancement, 326 patches and 1676 defects and tasks. Other issues are for example crash reporter issues, which can be tracked currently inside Sun only. In sum many more CWS are integrated and can be queried in EIS. Because all CWS after the branch of OOE (OOo2.2) and all CWS from OOF (OOo2.2.1) are copied also in this trunk.

A comparison of the numbers with the last feature release of OOo 2.1 and OOo 2.2 shows the CWS numbers aren't double but the numbers of issues are more than double.

Release	CWS	Issues	dev. time
OOo 2.1	197	841	3 months
OOo 2.2	221	948	3 months
OOo 2.3	370	2491	6 months

This is a result of 2 big new feature, where more than 100 issues are registered at the CWSs. The first is the new Chart and the second the Report Builder.

CWS numbers :
As written above 370 CWS are integrated into code line for OOo 2.3. Also all CWS for OOo 2.2.1 and some CWS which are integrated after the split of branch of OOo 2.2.. The following charts show how many CWS and issues were integrated into the different milestones.

One highlight is perhaps m213. In this milestone nearly only the new Chart module was integrated with more than 300 issues registered at the CWS chart2mst3. Feature Freeze was round about milestone m221 and Code Freeze was at m225.

Crash reports :
In OOo 2.3 issues for more than 100.000 crash reports from older OOo releases and developer milestones are fixed. This is another step forward in the overall stability of OOo. But we have to be realistic, all crashes never be fixed!

Summary :
In this release many older bugs and feature are fixed and integrated. It was worked also on older regressions and on the general stability. But from quality perspective we have still to much regressions in the release cycle. We found it often very late (but in time) or after the release. When we will hold the time lines for Feature Freeze better and do not integrate such a mass before this date, than we can hold the release due dates next time too.

But in my opinion we hold the quality standard which makes OOo so successful. So do not hesitate to update to the new release of OOo or download the patches from Sun for StarOffice.

tags: openoffice.org quality statistics