Summary: | Incorrect bug list on Wiki page | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | penttila <penttila> |
Component: | Libreoffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | cloph, qubit, vstuart.foote |
Version: | 4.2.7.2 release | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
penttila
2014-11-01 12:34:10 UTC
Sorry, but the list is correctly titled "Bugs fixed against 4.2.7 RC1" and populated with https://bugs.libreoffice.org/show_bug.cgi?id=79269 If you are interested in all "most annoying" categorized bugs open against the 4.2 branch, you need to review the query linked in Reported bugs. That is: https://bugs.libreoffice.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&version=4.2.0.0.alpha1%2B%20Master&version=4.2.0.0.beta1&version=4.2.0.0.beta2&version=4.2.0.1%20rc&version=4.2.0.2%20rc&version=4.2.0.3%20rc&version=4.2.0.4%20rc&version=4.2.1.1%20rc&version=4.2.2.1%20rc&version=4.2.3.1%20rc&version=4.2.3.2%20rc&version=4.2.3.3%20rc&version=4.2.4.1%20rc&version=4.2.4.2%20rc&version=4.2.5.1%20rc&version=4.2.5.2%20rc&version=4.2.6.1%20rc&version=4.2.6.2%20rc&version=4.2.6.3%20rc&version=4.2.7.1%20rc&version=4.2.7.2%20rc&product=LibreOffice Should note that that is NOT a comprehensive list of all bugs open against LibreOffice 4.2 I would ask that you please revisit bug 82091 and test it against the 4.2.7.2 final release. And perhaps again with the current 4.3.3.2 release, or even a Prerelease 4.4.0alpha build and report status there. And if the issue has been resolved close out the bug as WORKSFORME on the newer releases. Closing. Sorry, looking closer you were correct. Have corrected the query on the Wiki to be: https://bugs.libreoffice.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&version=4.2.0.0.alpha1%2B%20Master&version=4.2.0.0.beta1&version=4.2.0.0.beta2&version=4.2.0.1%20rc&version=4.2.0.2%20rc&version=4.2.0.3%20rc&version=4.2.0.4%20release&version=4.2.1.1%20release&version=4.2.2.1%20release&version=4.2.3.1%20rc&version=4.2.3.2%20rc&version=4.2.3.3%20release&version=4.2.4.1%20rc&version=4.2.4.2%20release&version=4.2.5.1%20rc&version=4.2.5.2%20release&version=4.2.6.1%20rc&version=4.2.6.2%20release&version=4.2.6.3%20rc&version=4.2.7.1%20rc&version=4.2.7.2%20rc&version=4.2.7.2%20release&product=LibreOffice (In reply to V Stuart Foote from comment #2) > Sorry, looking closer you were correct. Have corrected the query on the Wiki > to be: > https://bugs.libreoffice.org/buglist. > cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=AS > SIGNED&bug_status=REOPENED&version=4.2.0.0.alpha1%2B%20Master&version=4.2.0. > 0.beta1&version=4.2.0.0.beta2&version=4.2.0.1%20rc&version=4.2.0. > 2%20rc&version=4.2.0.3%20rc&version=4.2.0.4%20release&version=4.2.1. > 1%20release&version=4.2.2.1%20release&version=4.2.3.1%20rc&version=4.2.3. > 2%20rc&version=4.2.3.3%20release&version=4.2.4.1%20rc&version=4.2.4. > 2%20release&version=4.2.5.1%20rc&version=4.2.5.2%20release&version=4.2.6. > 1%20rc&version=4.2.6.2%20release&version=4.2.6.3%20rc&version=4.2.7. > 1%20rc&version=4.2.7.2%20rc&version=4.2.7.2%20release&product=LibreOffice Hi V Stuart Foote! First of all thanks for the fix, this solves my original problem. On the other hand I realised now something else. The logical meaning of 'full list of reported bugs' should contain all bug against 4.2.X in any 'Status' without regarding to their 'Resolution'. An other solution can be to rename this search criteria for example to 'full list of unsolved problems'. @penttila, *, Yes your right, the context of the query in the release notes--adjacent to the "Most annoying Bugs" retrieval--makes more sense to return only unresolved issues against the build. For anyone with sufficient interest, the Resolved issues can be easily dug out from BZ. So, I'd probably go with the second. Adding a couple of the release managers who generate these wiki release notes so they know to tweak their steps. Stuart |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.