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 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
- (Optional:) Search Bugzilla, to see whether your issue has already been reported.
- Go to https://bugs.meego.com/enter_bug.cgi and choose the appropriate classification and product in which the bug happens. If you are unsure, just guess.
- Note: For feature/enhancement requests, please always use the classification "MeeGo Features".
- On the next page:
- Choose the Component in which the bug happens.
- Choose the MeeGo Release in which the problem was found. To find out:
- MeeGo version: enter in terminal:
cat /etc/meego-release
- Kernel version: enter in terminal:
uname -a
- Choose the Severity according to the definition.
- 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.
- In case you have time, check whether some existing 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.
- In the Description field, please try to fill in all data requested in the template, as text.
- List the exact steps to reproduce the bug, step by step, click by click, so it is easy to reproduce by testers. For example, instead of paraphrasing commands by saying: "suspend the system or put system to S3" we prefer to see the exact command like "echo mem >/sys/power/state" as steps to reproduce.
- Describe the current outcome and the expected outcome. Try to avoid writing "See screenshot" or "See attached file" but describe it briefly in words so it can be found when querying for existing bug reports (this helps avoiding duplicate reports).
- (Optional:) Add an Attachment such as a testcase, or a screenshot in case it makes sense.
- Click Commit.
- You are done - Thanks for your report!
Good practices and Guidelines
- Each bug report is for only one issue. If you find several issues, please separate them into several reports.
- DO NOT reopen if the same issue is found again after more than 2 weeks. Instead, create a new bug report with “[REG]” as a prefix in the summary.
- Do search before you file a bug - Try to avoid filing duplicates by taking a look whether your issue has already been filed before.
- Keep it clean:
- Don't start endless debates on topics not directly related to the scope of a specific bug report, for example release engineering or marketing. We have forums and mailing lists for that.
- Avoid quoting complete previous comments by stripping unneeded lines.
- Avoid answering above the quoted text.
- The admins Rule: Ultimately, the admins reserve the right to block your account. See our process for dealing with violations for more details.
1.2.0/1.2.1 Bug Tracking Process
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:
- 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