m (→Reporting an issue) |
(→1.2.0/1.2.1 Bug Tracking Process) |
||
| (3 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | =Getting started: Creating an Account= | + | ==Getting started: Creating an Account== |
All you need is an account to be able to file and comment on reports. The http://bugs.meego.com authentication system is integrated with the http://meego.com authentication system, so the same account is used for both sites. To create a MeeGo account visit the [http://meego.com/user/register registration page]. Soon after you will receive an email with a link that must be visited to confirm your account creation. You will have to change your password on meego.com before attempting to log into Bugzilla. | All you need is an account to be able to file and comment on reports. The http://bugs.meego.com authentication system is integrated with the http://meego.com authentication system, so the same account is used for both sites. To create a MeeGo account visit the [http://meego.com/user/register registration page]. Soon after you will receive an email with a link that must be visited to confirm your account creation. You will have to change your password on meego.com before attempting to log into Bugzilla. | ||
| - | =Reporting an issue= | + | ==Reporting an issue== |
* (Optional:) [https://bugs.meego.com/query.cgi Search] Bugzilla, to see whether your issue has already been reported. | * (Optional:) [https://bugs.meego.com/query.cgi Search] Bugzilla, to see whether your issue has already been reported. | ||
| Line 15: | Line 15: | ||
** Choose the type of '''Hardware''' (like Netbook, Nettop, Notebook, Handset, Automotive, TV). | ** Choose the type of '''Hardware''' (like Netbook, Nettop, Notebook, Handset, Automotive, TV). | ||
** If you know, choose the hardware '''Architecture''' (For example: N900 is ARM, most Netbooks are IA). Else leave it untouched. In case you test on a N900 please add the keyword ''N900''. | ** If you know, choose the hardware '''Architecture''' (For example: N900 is ARM, most Netbooks are IA). Else leave it untouched. In case you test on a N900 please add the keyword ''N900''. | ||
| + | ** In case you have time, check whether some existing '''[https://bugs.meego.com/describekeywords.cgi keywords]''' apply to your issue, and add them. | ||
** Enter a '''Summary''' describing the bug. A good summary should be straightforward and precise, to clearly identify the issue. This also helps avoiding duplicate reports. | ** Enter a '''Summary''' describing the bug. A good summary should be straightforward and precise, to clearly identify the issue. This also helps avoiding duplicate reports. | ||
** In the '''Description''' field, please try to fill in ''all'' data requested in the template, as text. | ** In the '''Description''' field, please try to fill in ''all'' data requested in the template, as text. | ||
| Line 23: | Line 24: | ||
* You are done - Thanks for your report! | * You are done - Thanks for your report! | ||
| - | = Good practices and Guidelines = | + | == Good practices and Guidelines == |
* Each bug report is for only one issue. If you find several issues, please separate them into several reports. | * Each bug report is for only one issue. If you find several issues, please separate them into several reports. | ||
| Line 34: | Line 35: | ||
* The admins Rule: Ultimately, the admins reserve the right to block your account. See our [[Community guidelines|process for dealing with violations]] for more details. | * The admins Rule: Ultimately, the admins reserve the right to block your account. See our [[Community guidelines|process for dealing with violations]] for more details. | ||
| - | =See Also= | + | == 1.2.0/1.2.1 Bug Tracking Process == |
| + | In order to align with [http://wiki.meego.com/Release_Engineering/Plans/1.2 MeeGo 1.2 release plan ], QA add a new value "1.2.0" in "MeeGo Release" field to track 1.2.0 update bugs. So for MeeGo 1.2.0 update and MeeGo 1.2.1 release, we will have 2 field: "1.2.0" and "1.2" to track related bugs: | ||
| + | * MeeGo Release = 1.2.0: if new bug is found in MeeGo 1.2 final release or 1.2.0 update, new bug should be reported to 1.2.0; | ||
| + | * MeeGo Release = 1.2: if new bug is found in MeeGo 1.2.1 release or 1.2.1 update, such as 1.2.0.9X image, new bug should be reported to 1.2.1; | ||
| + | * For current existed bug in 1.2, we will keep the MeeGo release version unchanged. If we found one existed bug in 1.2 need to be fixed in 1.2.0 update, QA will clone one bug to 1.2.0 version; | ||
| + | * MeeGo 1.2.0 update team will only focus on MeeGo Release = "1.2.0" bug fix and verification. | ||
| + | |||
| + | ==See Also== | ||
* [[Quality/Bugzilla_Fields|Fields in a bug report]] | * [[Quality/Bugzilla_Fields|Fields in a bug report]] | ||
* [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]] | * [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]] | ||
* [[Quality/Bugtriage|MeeGo Bug Triage]] | * [[Quality/Bugtriage|MeeGo Bug Triage]] | ||
| + | |||
| + | [[Category:QA]] | ||
Contents |
All you need is an account to be able to file and comment on reports. The http://bugs.meego.com authentication system is integrated with the http://meego.com authentication system, so the same account is used for both sites. To create a MeeGo account visit the registration page. Soon after you will receive an email with a link that must be visited to confirm your account creation. You will have to change your password on meego.com before attempting to log into Bugzilla.
cat /etc/meego-release
uname -a
In order to align with MeeGo 1.2 release plan , QA add a new value "1.2.0" in "MeeGo Release" field to track 1.2.0 update bugs. So for MeeGo 1.2.0 update and MeeGo 1.2.1 release, we will have 2 field: "1.2.0" and "1.2" to track related bugs: