Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Petr

IMHO, community can't support too many stable versions. Customers who
need it, have to pay someone for it. We should leave 3.3 and concentrate
on making 3.5 the best release ever.

I couldn't agree more. But someone made up this concept of "rock
solid" and "Enterprise ready". To make things more confusing there are
two versions on the download page that are "Enterprise ready" and
there isn't anyone who can say which are the differences and which one
should companies adopt...
E.g.
http://nabble.documentfoundation.org/Differences-between-LibreOffice-3-3-and-3-4-tt3518436.html

The reason for my post is that family 3.3 will no longer be updated
and the ONLY version this Community is "selling" as "Enterprise ready"
will be version 3.4.5

I think that there is no need for panic :-) 3.4 has been out since, Jun
1, 2011. We did 4 bug fix releases. There was plenty of time to escalate
bugs that would break people from using this version and there were many
possibilities to get these fixes.

Currently there are two "rock solid" versions. And you can see from
the comments at the forum that many people (and companies) were
sticking with version 3.3.x just to be on the safe side (maybe that is
why there are not more bug reports for 3.4.4?)

I'm not in panic. I was just sharing my concern. If you guys aren't
worried why should I be?

Best regards,
Pedro

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.