| Summary: | Stabilize =app-office/openoffice-3.1.1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Robert Buchholz (RETIRED) <rbu> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | djcater+gentoobugs, java, nikoli, nirbheek, pacho, robbat2 |
| Priority: | High | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 270947 | ||
| Bug Blocks: | 280393 | ||
|
Description
Robert Buchholz (RETIRED)
2009-08-21 06:37:44 UTC
(In reply to comment #0) > Andreas, what is the status of OpenOffice 3.1.0 ? Is it ready for primetime? > We're going stable with xulrunner 1.9.1, so judging by dependencies we would > need it stable as well. > In my opinion: Very ready for primetime, wanted to propose it for stabilization myself in the next days. Robin/Java, are these good for stable? dev-java/lucene:2.3 dev-java/lucene-analyzers:2.3 +1 on stabilizing the 2.3 slot of Lucene. If you can safely do SLOT=2.4 instead, that would be even better. I guess in light of bug #283370 we should target 3.1.1 for stabilization instead So in the end, 3.1.0-r1 or 3.1.1 ? I think that 3.1.1 should be the version to stabilize. For now, I updated succesfully to it in one of my systems (that was using 3.0.1 due an upstream bug in 3.0.0 until it was dropped from the tree :-( ) (In reply to comment #5) > So in the end, 3.1.0-r1 or 3.1.1 ? > Yes, definitely 3.1.1, no use in stabilizing a release with multiple security issues (and 3.1.1 is a bugfix release of 3.1.0 anyway, so backporting the fixes is useless IMHO) Alright then, we'll handle this in the security bug *** This bug has been marked as a duplicate of bug 283370 *** |
