Waiting for AOO

Posted Aug 2, 2017 22:35 UTC (Wed) by rahvin (guest, #16953)
In reply to: Waiting for AOO by vbabka
Parent article: Waiting for AOO

I concur, continuing to allow an known insecure product with no capability to fix those security issues should be evidence enough to shut down the downloads and redirect to LO until the issue is solved by development improving or shutting down the project. Everyone of those downloads will potentially destroy the Apache name for someone unaware that OO is essentially abandonware. Until Apache can fix the issue they should halt binary downloads and redirect to LO.

Waiting for AOO

Posted Aug 6, 2017 20:31 UTC (Sun) by cornelio (guest, #117499) [Link] (1 responses)

That just won't happen (redirecting to LO).

LO and AOO are for all purposes different projects and the Apache Software Foundation can't make any claims on the quality or suitability of external projects. What could happen, if they don't release new code, is that the project would be moved to the "Attic" in which case the software would still be made available with a note that it is being EOL'ed.

Waiting for AOO

Posted Aug 6, 2017 23:39 UTC (Sun) by donbarry (guest, #10485) [Link]

Not that it's likely to happen, but let's be honest, it's not "can't", it's "won't". Of course they can make statements about the quality or suitability of external projects.