QA/FAQ: Difference between revisions
→How to assign a bug (QA team only): How to assign |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 110: | Line 110: | ||
=== How to assign a bug (QA team only) === | === How to assign a bug (QA team only) === | ||
It has become a de-facto standard to proceed as following: | It has become a '''new''' de-facto standard to proceed as following: | ||
* User Account of ''[[FindTheExpert|Friendly Expert]]'' (or known developer for the issue) will be inserted to '' | * User Account of ''[[FindTheExpert|Friendly Expert]]'' (or known developer for the issue) will be inserted to ''CC'' by an experienced user, Status remains (or becomes) ''New'' | ||
* Developer accepts bug and | * Developer accepts bug by adding himself to "Assigned to" and changing Status to ASSIGNED (or does not accept bug) | ||
The following queries will have to be modified! | |||
* <span class="plainlinks"> QA survey, a bug may not leave for a [https://bugs.freedesktop.org/buglist.cgi?chfieldto=-30&query_format=advanced&emailassigned_to1=1&chfield=assigned_to&chfieldfrom=2010-11-30&bug_status=NEW&email1=libreoffice-bugs%40lists.freedesktop.org&product=LibreOffice&emailtype1=notequals too long time] without ''[https://bugs.freedesktop.org/buglist.cgi?emailassigned_to1=1&query_format=advanced&bug_status=NEW&email1=libreoffice-bugs%40lists.freedesktop.org&product=LibreOffice&emailtype1=notequals Accepted]''</span> | * <span class="plainlinks"> QA survey, a bug may not leave for a [https://bugs.freedesktop.org/buglist.cgi?chfieldto=-30&query_format=advanced&emailassigned_to1=1&chfield=assigned_to&chfieldfrom=2010-11-30&bug_status=NEW&email1=libreoffice-bugs%40lists.freedesktop.org&product=LibreOffice&emailtype1=notequals too long time] without ''[https://bugs.freedesktop.org/buglist.cgi?emailassigned_to1=1&query_format=advanced&bug_status=NEW&email1=libreoffice-bugs%40lists.freedesktop.org&product=LibreOffice&emailtype1=notequals Accepted]''</span> | ||
*<span class="plainlinks">QA survey, Bugs | * <span class="plainlinks">QA survey, CONFIRMED NEW Bugs that have not ''[https://bugs.freedesktop.org/buglist.cgi?chfieldto=-45d&chfield=bug_status&emailassigned_to1=1&query_format=advanced&chfieldfrom=2010-11-30&list_id=42246&chfieldvalue=NEW&field0-0-0=commenter&bug_status=NEW&email1=libreoffice-bugs%40lists.freedesktop.org&type0-0-0=anywordssubstr&value0-0-0=LibreOffice%40bielefeldundbuss.de%20%20%20detective.conan.1412%40gmail.com%20%20iamtester8%40gmail.com%20jbf.faure%40orange.fr%20%20jr%40natural-computing.de%20%20fyvaao%40ya.ru%20%20vitriol_vitriol%40katamail.com%20%20gerard.fargeot%40orange.fr%20%20bugs%40eikota.de%20andre.schnabel%40gmx.net%20drew%40baseanswers.com%20%20%20maand%40gmx.de%20%20wope%40gmx.com%20%20baur.steven%40googlemail.com%20%20dmx404%40gmail.com%20jeffdchang%40gmail.com%20%20yfjiang%40novell.com&product=LibreOffice&emailtype1=exact not found an assignee within 6 weeks]''</span> | ||
=== Bug still visible although bug status FIXED? === | === Bug still visible although bug status FIXED? === | ||
Revision as of 12:53, 29 February 2012
Here you find answers to Frequently Asked Questions
Bugzilla HowTos
How do I report a Bug?
If you believe to have found a bug in Libreoffice please follow the instructions here: How to Report Bugs in LibreOffice.
Are "nightly builds" available?
Yes, but we call them Daily Builds. More information on Testing Daily Builds.
How do I find information I need?
Here you can find several useful queries:
- [1] still waiting for a developer
- Bugs waiting for QA Review
For users of 64-bit operating systems
It is possible to run 32-bit applications on 64-bit operating systems. This might make the Platform chooser in Bugzilla a bit confusing. In general, please enter what your version of LibreOffice was built for. This information is sadly not visible in the application, however:
- Windows users: there is currently no official 64-bit version. You are most probably using a 32-bit version, use "x86 (IA32)". Please mention your operating system under Description.
- Linux users: in most cases you should be using a 64-bit version of LibreOffice, if your system is also 64-bit. Your package manager might give further hints. It's most probable that you can use "x86-64 (AMD64)".
- Mac OS users: ...
How to Duplicate a bug

If you find out that a Bug (for example fdo#40691 is a DUPLICATE of an other one (fdo#37195) you can mark the duplicate Bug (fdo#40691) as DUP inserting the number of the remaining bug (37195) into the pane opening when you click Mark as Duplicate. It is not necessary to transfer reporter and CC list to the remaining fdo#37195, because Bugzilla will send information to all changes in remaining Bug 37195 to reporters and CC of duplicated bugs. Generally the latest report will be marked as a DUP of a more early report, except the new report contains more information or has a more advanced status (Assigned).
How to use Status or Keyword NEEDINFO
Status NEEDINFO should be used if information in the report is not sufficient.
If the bug has already been assigned and you find out that more information will be required, you should not change the Status, but use the Keyword NEEDINFO to make clear your request.
Currently Status Needinfo is not mentioned in Bugzilla Help, because the Help is for New Default Status Workflow, please also see fdo#42142!
How to terminate a Bug if it can't be reproduced any longer
If a bug has been confirmed, but the problem vanished with a later LibreOffice version, do not use Resolved Fixed, what is reserved for bugs with a real reviewed Fix. The appropriate Status for a Bug where the problem simply vanished is Resolved WORKSFORME. Reason: A reviewed Fix is a much more reliable solution that an unknown reason for a vanished problem, this difference should be visible in the Status information. The Version where the bug can no longer be reproduced should be mentioned in the Whiteboard as Target
How to use subcomponents
On BugReport Details lots of subcomponents are listed with links to Bugzilla Search and Bugzilla bug submission. In the following you find hints for what kind of problems what Subcomponents should be used in the Bugzilla' Subject line. In the following listing a click on the Sub Component heading will start a Bugzilla query for that sub component.
BUGZILLA
Only in component WWW for FDO Bugzilla related problems.
BUGZILLAASSISTANT
Only in component WWW, for problems related to the LibreOffice specific Bug Report Assistant. May be you want to learn some more about this tool here?
CONFIGURATION
Use for instance, if the configuration of LibreOffice applications (WRITER, DRAW, CALC, ...) is broken or if the Installation associates file extensions wrongly.
EXTENSIONSWEBSITE
Only in component WWW: for problems with the LibO Extensions-website
FILEOPEN
For all problems related to opening documents, as well as for problems when opening non-ODF file types like MS-Office, XHTML or XML, Picture formats like PNG, SVG, WMF, ...
FILESAFE
Typo, please correct to FILESAVE if you find reports with FILESAFE in the subject line!
FILESAVE
For all problems related to saving documents, as well as for problems when exporting to the file types XHTML or XML and Picture formats like PNG, SVG, WMF, ...
HYPHENATION
Only in component Linguistic: for problems with the LibO Libhyphen Hyphenator.
IDE
Only available for Component BASIC for problems with the Integrated Development Environment like broken search function or similar.
MAILING
Only in component WWW: for problems with the LibO Mailing Lists, like bounced postings, submit/unsubmit problems, ...
MAILMERGE
For problems with the LibreOffice Mailmerge function from menu 'Tools -> Mail Merge Wizard' or with the Form Letter function in menu 'File -> Print'.
MinGW
MinGW (Minimalist GNU for Windows) is a free toolchain based on GCC (the GNU Compiler Collection). So far we are using the Microsoft VisualStudio C++ compiler to provide the Windows builds, but the intent is to switch to MinGW to produce the Windows binaries. At the current stage, the MinGW builds start, and are somewhat usable, but contain bugs, and need testing.
Bugs should be marked with MinGW only when they appear in the builds from http://dev-builds.libreoffice.org/daily/MinGW_cross-compilation/master/ , but not in other Windows, or Linux builds.
Please note that MinGW builds are binary incompatible with the http://en.wikipedia.org/wiki/MSVC MSVC], which means that extensions written in C++ built with MSVC cannot work in MinGW builds.
MIRRORS
Only appropriate with Component WWW! If the automatic download forward leads to an empty page, You get other error messages, download speed is too slow, ... Name and URL of the mirror will be required.
For PDF export problems only visible in one component like Drawing, Presentation, Spreadsheet or Writer.
RTL
For all text direction Right To Left related problems. If the problem is limited to a particular localization or language, please ad localization or language in square brackets like [AR] in the summary line. We have Bug fdo#43808 - (rtl-meta) Meta bug for Most Annoying RTL related issues.
SLIDESHOW
For problems only visible during running presentation, but ok in Presentation edit mode. Also appropriate for problems visible in custom animation preview.
SPELL
Only in component Linguistic: for problems with the LibO Hunspell Spell Checker.
THESAURUS
Only component Linguistic: for problems with the LibO OpenOffice.org New Thesaurus.
VIEWING
Use, if document contents are not shown (correctly) on the screen, but print and PDF export look ok. An additional indication might be that other LibreOffice or OpenOffice versions correctly show the contents on screen, meaning it's not a problem with the document itself.
How to assign a bug (QA team only)
It has become a new de-facto standard to proceed as following:
- User Account of Friendly Expert (or known developer for the issue) will be inserted to CC by an experienced user, Status remains (or becomes) New
- Developer accepts bug by adding himself to "Assigned to" and changing Status to ASSIGNED (or does not accept bug)
The following queries will have to be modified!
- QA survey, a bug may not leave for a too long time without Accepted
- QA survey, CONFIRMED NEW Bugs that have not not found an assignee within 6 weeks
Bug still visible although bug status FIXED?
You can not be sure whether the Fix has been integrated into the next release. Please see Target information in Whiteboard or GIT link.
RC Version vanished?
You filed a Bug and can not find it with "Search by Version" (for example using a link you bookmarked)? Reason might be that you discovered the bug with the last Release Candidate before the release. If the LibreOffice Release version is bit by bit identical to the last RC, the RC version from Version Picker will be changed to Release Version (for Example: 3.4.2 RC to 3.4.2 release by the administrator
Bugzilla Voting?
Currently the Engineering Steering Committee does not believe that a simple Voting will bring enough new information. That does not mean that there is a fundamental resistance against any way of "user poll". If someone has an well founded conclusive concept we can discuss the question again and if feedback is positive we will find an infrastructure for the process. We have an experimental Vote_for_Enhancement, but user interest seems not to be big, and current use is far away from intention to find good arguments instead of counting votes.
Useful Bugzilla Statistics
May be Following FDO Bugzilla statistics are interesting for you:
Weekly statistic (last 7 days)
General

Charts:
- New reports for what versions
- New reports for what Components
- New reports what bugs for what versions?
- New reports What reporter what component for what version?
Bugzilla Submission Asistant
- Bar Chart Component / Reporter: Valid Bugs reported with Bugzilla Submit Assistant
- Bar Chart Component / LibO Version: Valid Bugs reported with Bugzilla Submit Assistant
- Pie Cart Reporter: Valid Bugs reported with Bugzilla Submit Assistant
How to use information
Zipped attachments of Mac users
Contents has to be added
Integrated Bugfixes
LibreOffice 3.4.3 RC1
Please see here
We have a new low traffic mailing lists for all QA related announcements. You can subscribe here
Who should subscribe?
QA team members, users active in QA and everyone else interested in QA news.
Users frequently active in Bug confirmation or Bug reporting have been added for the first announcement concerning IRC Bug Hunting Session.
Who can post?
Only subscribers, the list is not public.
For what should libreoffice-qa be used?
Please only post mails with news of general interest for QA. For example
- Bugzilla handling news like new Subcategories, ...
- New test tools or available special LibO Test Builds
- New QA related projects or important progress for existing projects
- New Key Words
- other decisions
- Important modifications on Bugzilla help Wiki pages
- Invitations for IRC sessions
For discussions a thread should be opened in an appropriate mailing list (mostly: discuss@documentfoundation.org) and mentioned in the posting. Comments concerning announcements are unwanted.
How often?
Currently it's forseeable that there might be 1 to 3 announcements a week, we will see ...