It seems that all the bugs that were in Bugzilla as NEW have been bumped
back to NEEDINFO with the message
"This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2
prereleases.
Details on how to test the 3.5.0 beta1 can be found
at:http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1"
I have to say this is very irritating where a bug has been logged for
a long time
and re-affirmed may times for new versions of OpenOffice.org, originally,
and now LibreOffice.
That said, however, I am quite willing to test my bug in 3.5, but the
link above is
most unhelpful. What I need is a way to use 3.5 for testing, while
retaining the
current stable version for everyday use. Can someone help me with that? I am
using Ubuntu 11.10 32 bit on a HP desktop PC.
Tony
--
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
- [tdf-discuss] How do I test bug in 3.5 that have been bumped back to NEEDINFO · Tony Pursell
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.