Difference between revisions of "Using ROSA Bugzilla"
Pavel.shved (Talk | contribs) (→Update request tracking: add QA old report) |
Pavel.shved (Talk | contribs) (→Useful links) |
||
| Line 45: | Line 45: | ||
* [http://bugs.rosalinux.ru/buglist.cgi?f1=flagtypes.name&o1=substring&classification=ROSA%20Products&query_format=advanced&v1=secteam_verified%3F&list_id=1693 Update requests pending secteam approval] | * [http://bugs.rosalinux.ru/buglist.cgi?f1=flagtypes.name&o1=substring&classification=ROSA%20Products&query_format=advanced&v1=secteam_verified%3F&list_id=1693 Update requests pending secteam approval] | ||
* [http://bugs.rosalinux.ru/buglist.cgi?f1=flagtypes.name&o1=substring&classification=ROSA%20Products&query_format=advanced&v1=published%3F&list_id=1694 Update requests pending Repo-man approval] | * [http://bugs.rosalinux.ru/buglist.cgi?f1=flagtypes.name&o1=substring&classification=ROSA%20Products&query_format=advanced&v1=published%3F&list_id=1694 Update requests pending Repo-man approval] | ||
| − | * [http://bugs.rosalinux.ru/buglist.cgi?f1=flagtypes.name&o1=substring&query_based_on=qa_pending_week&o2= | + | * [http://bugs.rosalinux.ru/buglist.cgi?n2=1&f1=flagtypes.name&list_id=3974&o1=substring&query_based_on=qa_pending_week&o2=changedafter&query_format=advanced&f2=flagtypes.name&v1=qa_verified%3F&component=Localization&component=Main%20Packages&v2=7d&product=ROSA%20Linux&known_name=qa_pending_week Update requests that have been pending QA approval for more than a week] |
==== Feature and task tracking ==== | ==== Feature and task tracking ==== | ||
Revision as of 10:44, 3 September 2012
ROSA Bugzilla is located at http://bugs.rosalinux.ru/. The main purpose of this site is to serve as a central point of contact with distribution maintainers and developers about the problems in the ROSA Desktop distributions.
To file bugs there, you should "register" at Bugzilla itself, ABF credentials won't work.
Contents
- 1 What issues are tracked in ROSA Bugzilla?
- 2 How to report a bug
- 3 Accompanying mailing lists
- 4 How to propose a feature
- 5 Useful links
- 6 Security and business-sensitive issues
- 7 How to edit a comment
- 8 ROSA-sepcific features
- 9 What to do if there's a problem with the Bugzilla
- 10 For ROSA Employees
- 11 Notes
What issues are tracked in ROSA Bugzilla?
ROSA Bugzilla is used to track all "downstream" issues with ROSA Desktop, and some problems with ROSA Bugzilla infrastructure. Here's the list of issues you should file to the Bugzilla:
- Bugs in already released ROSA Desktop distributions;
- Bugs in packages and distributions that have not yet been released.
- Issues with ROSA collaboration infrastructure, such as forums, wiki and ROSA Bugzilla itself.
How to report a bug
The ROSA Bugzilla, though it has some specific tweaks, is just a usual bugzilla. The interface is most likely familliar to you: if you saw one issue tracker then you've seen them all.
To report a new bug, or to comment on an existing one, you should obtain an account first by registering at the bugzilla itself. ABF credentials do not work. ROSA corporate mail credentials do not work. Your can't register via your Facebook or Twitter account either. We tried to keep it simple.
After that, just click "New", select a product you wish to report bug (most likely, it will be "ROSA Linux")[1]. Specify the category you want to report the bug against; if unsure, select "Main Packages". When you report a bug, you should specify a package you have problems with; the bug filing form contains instructions on how to obtain this information. This information is used to determine the person responsible for fixing the bug[2]. Fill all the fields in the form, following the instructions listed nearby.
If you think your bug is sensitive, read this section.
Accompanying mailing lists
There are two mailing list useful to make the interaction with the bug tracker easier
- bugs@lists.rosalab.ru — notifications about all new bugs that aren't marked as "sensitive" (see here) and about changes made to them are sent to this list. You may subscribe at your own automatically here;
- private-bugs@lists.rosalab.ru — notifications about sensitive bugs are sent here. Only a ROSA employee may subscribe, via this form.
How to propose a feature
To propose a feature, open a new Bugzilla ticket in "Features" product. The feature will be reviewed by developers as soon as possible, and it will be decided if it's worth allocating resources at, or if the feature fits the overall concept of ROSA Desktop. Make sure you have searched for similar features (or reviewed the list of all features) because your proposal might have already been reviewed.
If the feature is so sensitive to ROSA business that it should be kept secret from the broad audience, select "ROSA employees" group restriction at the bottom of the bug.
See #Useful links for the list of feature-related queries.
Useful links
Bugzilla has an advanced bug search and filter mechanism, though it's not easy to use. I gathered some useful search queries here:
Update request tracking
- requests pending QA approval
- Update requests pending secteam approval
- Update requests pending Repo-man approval
- Update requests that have been pending QA approval for more than a week
Feature and task tracking
- All unconfirmed features
- all recently proposed features;
- all accepted features for 2012 Desktop release;
- all accepted features and important bugfixes for 2012 Desktop release;
- all features (regardless of their status;
Misc
Security and business-sensitive issues
If your issue is sensitive because
- you are reporting a security bug;
- you are a ROSA employee, contractor, or customer, and want to raise a business-sensitive issue;
you should click "ROSA Employees" checkbox at the bottom of the bug file form. This will make the bug visible to you and ROSA employees only.[3]
Warning! If you forget to set this checkbox, the bug comment will automatically be disseminated through a public mailing list, and you can't cancel it later. Please, be careful with this.
If you need greater security, contact admins; see #What to do if there's a problem with the Bugzilla.
How to edit a comment
There is no way to edit a comment in Bugzilla once it has been published. Post a new one instead.
Bugzilla comments are used to track the whole history of the work made on a bug. Editing a comment might also affect the responses to it, and whether an update was approved/rejected. That's why we would turn off the ability to edit comments even if it was present in the stock Bugzilla.
ROSA-sepcific features
ROSA Bugzilla has a number of tweaks that aid us in the development process of ROSA linux distribution. Here's a list of them.
Update Request checkbox
The process of updating a released ROSA Linux distribution is built on top of Bugzilla. You can read more in Requesting an Update policy. An interface of bugzilla was extended with a "Request for Update" checkbox. The value of this checkbox denotes whether this bug is also an update request. The checkbox also helps you to fulfill the requirements of the Requesting an Update policy by disabling itself if your comment doesn't have enough information.
When you set this checkbox, the QA (or some other party your update had issues with, Security team, for instance) is notified about the change, and will process your update in a timely manner. By changing the checkbox state and committing your change you may notify QA if the package is ready (if you set the checkbox), or cancel the request (if you unset the checkbox).
To aid QA teams in reading the bug comments efficiently, we added a filter that expands only update-related comments. These are comments that contain the keyword "advisory" or a link to ABF build list. To use the filter, you must have Javascript enabled in your browser.
Highlighting Update Request comments
Comments that may be related to update requests are highlighted with a greener color, so they can be identified easier in a (possibly) long comment stream. See the screenshot for an example.
Please, note that this only works with the default "Dusk" theme!
Common transitions for ROSA teams
Some transitions in the process of update verification are too common to make the team members make many clicks during common operations. Some buttons were added that use Javascript to switch flags and statuses after a QA, secteam or repo-man have worked on the package.
Note that these buttons do not save changes, they just switch the status. To save the changes you should click "Save Changes" and write a comment!
Only buttons relevant to a specific team are displayed. The screenshot to the right is just an illustration that gathers them all in a single screen.
ROSA Desktop products have "ISO-related" checkbox. The flag should be used by release-managers to mark bugs they will look through when assembling an ISO. As soon as the bug is fixed in ISO, this flag may be removed.
Here is a query to list all bugs with this checkbox set.
What to do if there's a problem with the Bugzilla
If you have successfully obtained an account, and want to report a broken link, or a problem with Bugzilla functionality, or want to ask for specific permissions, please, open a bug in "Bugzilla" component of "Websites" product.
Administrators
You may also directly contact bugzilla admins, but we prefer that all requests are directed to the bugzilla itself as described above.
Bugzilla administration: Pavel Shved
Networking issues: Vladimir Mironov
For ROSA Employees
If you have problems with accessing bugzilla[4], or wonder what e-mail and password to use, please, refer here.
Notes
- ↑ The hints and design of the "New bug" page was inspired by Mandriva Bugzilla, and some texts were borrowed from there.
- ↑ This is not yet implemented, but is coming very soon, by the end of May 2012.
- ↑ In case you're worried about this, "QA contact" field will automatically be reset to a private mailing list in this case".
- ↑ for instance, you get a "Server not found" error.
