QA/BSA: Difference between revisions
complete data sources and scripts |
|||
| Line 25: | Line 25: | ||
== Data sources == | == Data sources == | ||
* https://bugs.freedesktop.org/query.cgi?product=LibreOffice&query_format=advanced | * https://bugs.freedesktop.org/query.cgi?product=LibreOffice&query_format=advanced : [http://dachary.org/wp-uploads/2011/09/query.txt list of components and list of versions]. | ||
* http://wiki.documentfoundation.org/ | * http://wiki.documentfoundation.org/BugReport_Details : [http://dachary.org/wp-uploads/2011/09/component_comments.txt component comments] and [http://dachary.org/wp-uploads/2011/09/subcomponents.txt subcomponents for each component] extracted using [http://dachary.org/wp-uploads/2011/09/libreoffice-bug.html a microformat]. | ||
A [http://dachary.org/?p=860 technical report] explains in more details how these scripts are used to collect the parts of a bug report frontend. | |||
== Additional information == | == Additional information == | ||
Revision as of 22:15, 4 September 2011
Draft
A volunteer has been found to create a (Javascript) Assistant what will ease bug reports on Fedesktop.org Bugzilla. Some first modules you see here and here.
Release plan
Milesone 0.1
A simple placeholder, so that a "Report a bug" link added to LibO Help menu will not lead to Nirvana, but to an existing Web page with a forward-link to he LibO bug submit page, eliminating some problems: The Submission page for all Projects is https://bugs.freedesktop.org/enter_bug.cgi Projekt LibO there has a link to https://bugs.freedesktop.org/enter_bug.cgi?product=LibreOffice That's not good, Initial status should be UNCONFIRMED, and user should select a LibO version, not report with random Version from Bugzilla. That will be reached with https://bugs.freedesktop.org/enter_bug.cgi?product=LibreOffice;bug_status=UNCONFIRMED;version=?. I simply added ";bug_status=UNCONFIRMED" to define Initial Status and ";version=?" to delete any Versions selection from picker.
The only thing the bug reporter / user will see of that all is "if forward will not work please click here".
For that we need some Webspace on the LibO servers(?), the rest can be done easily. For later milestone some administrative questions will have to be kept in mind, for example admin permissions for Porgrammer, ... .
- Planned release date: ASAP
Milestone 0.2
Minimum Version, Automated proceeding of BugReport_Details:Selection of correct Component and Subcomponent, user can only submit if he checked for DUPlicates before. The Assistent should have "LibO Webseite look"
- Planned release date: Together With LibO 3.5.0 RC
Milestone 0.3
Adding features as shown in first example with influence to Severity / Priority pickers and and and (additional search in OOo, ...)
- Planned release date: January 2011
Data sources
- https://bugs.freedesktop.org/query.cgi?product=LibreOffice&query_format=advanced : list of components and list of versions.
- http://wiki.documentfoundation.org/BugReport_Details : component comments and subcomponents for each component extracted using a microformat.
A technical report explains in more details how these scripts are used to collect the parts of a bug report frontend.
Additional information
- Progress: QA-Projects-Incubator
- To Dos