Am 02.06.2012 16:46, webmaster-Kracked_P_P wrote:
There seems to be differenting opinions on how business ready 3.5.3 was
So now that LO 3.5.4 is out,
I ask the users, is it ready to be deployed to my/our business users?
We really need to know.
The last "official" word on the 3.5.x line was that business users would
research the package before downloading and installing it.
Well, I do not know how they will to all that research, or where they
will get the documentation for it, before downloading it.
So I am asking LO users the question.
Is 3.5.4 ready for our business and/or enterprise users?
The doc people are work hard to get more 3.5.x line documentation out,
but to be honest about it people can still use 3.3.x and 3.4.x docs till
3.5.x comes out.
What is the problem with 3.5? What are your conclusions when a user like
me or Tom states that everything is fine with 3.5? I am a completely
untypical user who skipped the whole 3.4 series after writing a bunch of
bug reports. Tom has an entirely non-technical view on the project. The
overall service quality of this particular user list is really bad.
The bug tracker can tell all unresolved issues that do exist in 3.5 but
not in 3.4? Don't ask me how. I file my bugs to the AOO tracker where it
serves both projects.
For unsubscribe instructions e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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