m |
(categorise) |
||
| Line 31: | Line 31: | ||
Most of us have submitted bugs in the past and forgotten about them. Take a look at them and check whether they still apply in the latest software version. | Most of us have submitted bugs in the past and forgotten about them. Take a look at them and check whether they still apply in the latest software version. | ||
Go to the [https://bugs.meego.com/query.cgi?format=advanced Query website] and make sure that under "Status" NEW, ASSIGNED and REOPENED are checked. Under "Email Addresses, Bug Numbers, and Votes", check the field "the reporter" and enter your email address below in the text field to query for them. | Go to the [https://bugs.meego.com/query.cgi?format=advanced Query website] and make sure that under "Status" NEW, ASSIGNED and REOPENED are checked. Under "Email Addresses, Bug Numbers, and Votes", check the field "the reporter" and enter your email address below in the text field to query for them. | ||
| + | |||
| + | [[Category:QA]] | ||
There are a number of ways to start triaging. If you have more ideas feel free to add them here.
Contents |
Pick up the product or component that interest you, or which you know about, or are willing to learn, or happen to use. You can query for existing open reports and take a look at issues that interest you, for example in order to update them by updating the Version field, or noting that they have been already fixed in the version you use (please mention the exact version that you use in a comment). If you want to constantly be informed about any changes, set up user watching by adding the "Default QA Contact" email address to your "User Watching" list. See this blogpost for bugs.maemo.org for a longer explanation about how this works.
Take a look at the latest incoming reports of the last two weeks (NEW and REOPENED state) and try to reproduce them, or ask for missing information, or add additional information. See the Triage Guide.
Many reported problems cannot be easily reproduced. Take a look at bug reports in NEW state, try to reproduce them, and feel free to add a comment either with instructions to reproduce or that you could not reproduce it and mention the version that you use.
| TO DO: Is this information accurate and correct? -- User:Andre |
Query for bug reports with an old MeeGo Release (Version) number and try to reproduce them with the latest software release to find out whether the reports are still valid. If they have been fixed in the meantime, you can add a comment about it.
| TO DO: Add link to Stock answers in case we introduce them, and add a "Update the stock answers" section here. -- User:Andre |
Clean up reports in NEEDINFO state that have not been changed for four weeks. This means that more information had been requested from the reporter but has not been provided. These reports should be closed as WORKSFORME if you are not able to reproduce, or as INVALID if there is simply not enough information to be a useful report. Please always explain your decision by adding a friendly comment and in the latter case, ask the reporter to provide the information asked for, if s/he can, and reopen the bug.
Example comment: "Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as WORKSFORME/INVALID. Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this in a recent version."
Most of us have submitted bugs in the past and forgotten about them. Take a look at them and check whether they still apply in the latest software version. Go to the Query website and make sure that under "Status" NEW, ASSIGNED and REOPENED are checked. Under "Email Addresses, Bug Numbers, and Votes", check the field "the reporter" and enter your email address below in the text field to query for them.