#2498 closed task (duplicate)
OpenOffice 3.1.0
| Reported by: | thomas | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Version upgrade to 2.4:
http://liquidat.wordpress.com/2008/03/27/openofficeorg-24-to-be-released-today/
Because OOo heavy in compiling and testing it might go to 7.0 and not to 6.3?
Change History (8)
comment:1 by , 16 years ago
| Milestone: | 7.0 → future |
|---|
comment:2 by , 16 years ago
comment:3 by , 16 years ago
| Milestone: | future → 6.4 |
|---|---|
| Summary: | OpenOffice 2.4 → OpenOffice 3.0.0 |
Version increment to 3.0.0
comment:4 by , 15 years ago
Consider using Go-oo version of OpenOffice due to license restrictions ins Sun's SCA. Plus gain better format support for OpenXML, WP Graphics, and MS Works, not to mention considerable speed increases. Go-oo is dual licensed under the LGPLv3 and CDDL.
comment:7 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
#3022 duplicates this bug, but more information contained there. Closing as a duplicate.
Note:
See TracTickets
for help on using tickets.
Given the OOo community's recent performance, I'd suspect that it would probably be a safe update, but since we can't say for sure, it still needs to be tested thoroughly. I just don't have the time right now to do any real testing on use of the suite. Because of it's size, it requires a few builds to test the the range of possible system dependencies, and last time I missed a few. Fortunately, our users caught them, and even provided fixes. Depending on the speed of the computer, compile times are drastically different from computer to computer. If anybody wants to tackle this monster before I get to it (historically, I have maintained the package in Tushar's absence), and after the 6.3 release, feel free. I think going forward, it would be wise to post a svn diff and request that the editing staff share the testing burden before commit.
-- DJ