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


Le 2012-05-18 22:52, John Hardy a écrit :
Tom;

It does just take time but it's not a que. It just depends on it
catching the eye of the devs. It might be worth askingt he devs list
what they think.
Apols and regards

Where might I find the devs list (and how to subscribe)? Thanks very much.

John


Before doing this, is there anyway to upgrade to the latest version of LibreOffice? I think the answer you will get on the dev list will be to upgrade to the latest supported version.

This will also allow us to test your bug report, confirm whether is happens on the latest version.

As far as the length of time goes, the triage of bugs does take time depending on the severity of bugs submitted. Also, most of the devs are volunteers and it does take some time for someone to either be assigned to it or for someone to pick it up.

The more people test it with descriptive results the quicker and easier it will be to fix or at the very least find a temporary workaround.

Cheers,

Marc




--
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.