The trouble is that they've already ceased their developer activity. That’s the entire point of Schaller's post. Look at what they're doing. They are serving u

The trouble is that they've already ceased their developer activity. That’s the entire point of Schaller's post. Look at what they're doing. They are serving up a Windows installer that is known to have a serious vulnerability: anyone can send an exploit in a HWP document with a .doc file extension, and an AOO user opening it will be pwned. The AOO "devs" know this is the case. Everyone downloading AOO 4.1.1 between April 2015 and August 2015, they have done them actual harm and installed a vulnerability on their machine. The fix is trivial: repackage the Windows installer minus one file. Instead of doing that one simple thing, they're posting excuses for not doing it. (If the answer is something like “well, Apache procedures make it difficult to just rerelease an installer minus one file”, then this would not be evidence in their favour - it would be evidence that the AOO bureaucracy actively hampers the interests of users and is not fit for purpose, and that Schaller's blog post is entirely correct.) You can’t expect people to take seriously claims that the project is not dead when they're actively harming their users by serving them software with a serious vulnerability for the past four months, and spending their time making excuses instead of fixing it.