I'm pretty disappointed in the Apache Foundation, to be honest, with their handling of the whole thing. It actually hurts LibreOffice and The Document Foundation in that regard - people remember OpenOffice but it's not a patch on LibreOffice while techy people automatically convert "Open" to "Libre" in their head whenever it's mentioned.Īpache really need to do the decent thing, and either license the name somehow or pull in the stables of LibreOffice and push them as OpenOffice. There's nothing in the licensing that would prevent that, as far as I know.Īnd splitting development effort like that is damaging to everyone, and people are STILL using the old name to search for the software they want, and then are bitterly disappointed at the state of it when they get it. Or remerge LibreOffice back into the fold, rename it to OpenOffice again and at least START on a level footing again. They can act as custodian for the name, maybe, but actually pushing the software forward is far beyond anything they've demonstrated they can do with it thus far. July 2020: 4.2.0 is the next minor release, planned to be released into a beta phase.Īpache were only embarrassing themselves with it from the day they took it over. Jan 2020: 4.2.0 is the next minor release, planned to be released into a beta phase. July 2019: 4.2.0 is the next minor release, planned to be released into a beta phase. July 2018: 4.2.0 is the next minor release, planned to be released into a beta phase within this year.įeb 2019: 4.2.0 is the next minor release, planned to be released into a beta phase. Jan 2018: The next major release will be 4.2.0 with a target to publish in 2018.
July 2017: Apache OpenOffice 4.2.0 is also planned for this year - but without to name a specific time frame Jan 2017: Apache OpenOffice 4.2.0 is planned for this year - but without to name a specific time frame
To save anybody else from skimming back, here is what AOO's official contributions to Apache's board have written about the smallest incremental feature release, AOO 4.2.0, something I argued that a healthy dev team ought to be able to get out the door in a few weeks back in 2016.
0 kommentar(er)
