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


On 12/13/2012 07:09 AM, webofht-libreoffice001@yahoo.com.hk wrote:
I think an office suite should be stable.

So, I think to emphasize the importance of quality assurance is vital.

May I suggest adding a step checking if the office suite starts properly?

LibreOffice should support most hardware and software configurations.

If it does not start in one case, please postpone and stop the release.

I'm one of the people really involved with QA and trust me, we do an abundant amount of testing on every release before and during production/patching. Just for an idea, we have an entire week being dedicated to LibO 4 testing:

http://www.pcworld.com/article/2019594/help-improve-libreoffice-4-0-in-a-test-marathon-this-month.html
http://wiki.documentfoundation.org/QA/Test_Marathon_LibreOffice_4.0

we're always looking for more help to test stuff from our user community, please get involved this week if you have a couple hours.

Best Regards,
Joel

Regards,
C. H. D.



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _


--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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

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.