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


@Paul, *,
This is a non-issue, please STOP.

 But,  just so it is clear in context Tanstaafl on this ML is the Charles in
fdo#76565 BZ  

Paul-6 wrote
I may be wrong, but as far as I have understood from Tanstaafl's posts,
there was no notice on the bug tracker that there was a test build
claiming to fix this, or at least no notice to the people connected to
the bug, at least until quite recently. If I'm wrong, then one can
debate about why he didn't notice this earlier and test it and post
back to the bug tracker so that the fix could be included in a release
build. But if my understanding is correct, then there is almost no way
that LO can claim they don't have egg on their face. Trying to divert
attention off them by blaming Tanstaafl isn't making the egg go away.

Stuart

-=ref=-
https://www.libreoffice.org/bugzilla/show_bug.cgi?id=76565#c14



--
View this message in context: 
http://nabble.documentfoundation.org/How-to-handle-regressions-tp4124391p4124706.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@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.