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

[tdf-discuss] Re: [Libreoffice-qa] Should I update to 3.?


Rainer Bielefeld píše v So 07. 04. 2012 v 19:05 +0200:
Hello,

very often we hear this question, and again and again we have to state 
that that question only can be answered by the questioner. How can we 
know what might be important for him and what not? For someone who never 
uses DRAW all Draw bugs are completely irrelevant, for me Bug 43752 and 
Bug 45848 are blockers.

I see the pain and agree with Cor. We need to be careful about
communication. It has to be positive (point to improvements) and also
realistic (point to existing bugs that might and need not cause troubles
to the user).

So after the question from someone who uses 3.4.5 and plans to update to 
3.5.2 I created a query showing all potential (known) blockers that 
might hinder someone who successfully uses 3.4.5 to update to 3.5.2

Why the query checks for bugs against "Master" and "Daily"? Are all of
these bugs in 3.5 as well?


Best Regards,
Petr


-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.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.documentfoundation.org/www/discuss/
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.