Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
OpenOffice.org Database
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas

Contributor graylion on OpenOffice.org Database

Use only stable openoffice version for LTS releases  
Written by mark_orion the 22 Jul 10 at 16:12. New
The OpenOffice 3.2 series contains serious bugs in the database component.
http://www.openoffice.org/issues/show_bug.cgi?id=108390
This bug as an example makes it impossible to do any serious database development with the 3.2 version.
This forum post confirms that releases with even minor numbers like 3.2 mainly focus on new features:
http://user.services.openoffice.org/en/forum/viewtopic.php?f=49&t=32644
40
votes
up equal down
Solution #1: Use only openoffice versions with odd minor number for LTS releases
Written by mark_orion the 22 Jul 10 at 16:12.
Releases focusing on stability have an odd minor number (e.g. 3.1.1, 3.3).
Releases with an even minor number (e.g. 3.2) are focusing on new features and are more prone to bugs. As an example the 3.2 release that is part of 10.04 Lucid has well known bugs in the database part. As office software is "mission critical", 3.2 should have not made it into Lucid.
24
votes
up equal down
Solution #2: Use recent release and keep sending bugfixes.
Written by Ssdg the 23 Jul 10 at 10:00.
So the LTS won't be outdated when the bug will be fixed. And make sure the bugs are fixed.
31
votes
up equal down
Solution #3: allow user to choose
Written by Goury the 24 Jul 10 at 21:31.
havin both branches with diff names will be excellent sollution (ex: ooo_stable, ooo_beta)

See the 2 comments or propose a solution (latest comment the 29 Jul 10 at 03:13) >>