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.
MeeGo Release field defines in which MeeGo version a bug has been found. Version names are defined according to the MeeGo release plan.
When bugs are in OPEN or RESOLVED status, it is used by the bug reporter to propose which milestone this bug is expected to be fixed.
Priority field describes the importance and order in which a bug should be fixed. It helps developers to prioritize their work. By default the priority is set as "Undecided" when reporting a new bug. The bug reporter could propose a priority in a comment. A dedicated bug triage team should set the initial priority for the bug while processing it as early as possible. Final priority setting would be decided by bug triage process. Priorities range from High (most important) to Low (least important).
The "Severity" field describes the impact of a bug, and the options include:
Please select the UX (like Netbook, Nettop, Notebook, Handset, Automotive, TV) that you identified the bug in. For bugs which apply to all UX (like bugs for Middleware/Core components), please select "All".
Please select the architecture (IA, ARM) that you identified the bug in. For example for N900 Base OS layer bugs this should be set to ARM. For bugs which apply for multiple architectures, like bugs for middleware or applications, please select "All".
1. Each bug report is for only one issue. If you find several issues in one test, please separate them into several bugs.
2. Write a precise summary (bug title). A good summary should be straightforward and precise, to clearly identify the issue. This also helps avoiding duplicate reports.
3. List the exact steps to reproduce the bug (bash commands, results after executing the commands etc, instead of only paraphrasing). For example, instead of paraphrasing commands by saying:
"suspend the system or put system to S3"
we prefer to see the following exact commands as steps to reproduce the bug:
echo mem >/sys/power/state
4. 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).
5. Reproducibility. For bugs which are not 100% reproducible, please provide an estimate of the probability of reproduction.
6. Impact to system or user. Provide a description of the actual impact to the system or user.
7. DO NOT reopen if same defect found again after more than 2 weeks. New bug report with “[REG]” as a prefix in the summary is mandatory.
8. NEEDINFO bugs should be assigned back to original bug reporter and NEEDINFO status should be removed after requested missing data has been provided in the report. NEEDINFO status should only be used for requests against the original bug reporter.
9. For "Target Milestone", when reports are in OPEN or RESOLVED status, it means to propose the bug to get fixed for a particular release; When verifying bugs, set the correct milestone where the bug is fixed.
Generally, the approved update release bugs must be fixed and verified in MeeGo Trunk firstly.
1. With Bugzilla, an approved release update (eg 1.1) bug must have a MeeGo bug entry in the latest release (eg 1.2) so QA can verify the latest (eg 1.2) Trunk build has the same bug fix on a target vertical platform.
2. With Bugzilla, an approved release update (eg 1.1) bug should have a bug in the latest release (eg 1.2) as a dependency (or blocker bug) to sure that the associated bug in the latest release is verified first.
3. Update release engineer should _not_ accept development patch submission for update release unless QA verified in Trunk build and mark the Bugzilla entry accordingly.
Of course, there are some exceptions that don't apply this guideline especially for those bugs in old releases are not applicable to latest release. For example:
1. Bug fixes in old releases' components where the latest release is using a different version;
2. Components used in old releases that are no longer used in trunk;
3. Security fixes that don't apply to the version in trunk, etc.
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in Bugzilla.
We have both techies and non-techies here and we both know we don't exactly speak the same language at all times. In case of missing information kindly tell reporters how to provide it, and/or point to https://bugs.meego.com/page.cgi?id=bug-writing.html in case of very vague reports (like "Can't send mail, plz help!!").
Try to avoid filing duplicates by taking a look whether your issue has already been filed before.
Ultimately, the admins reserve the right to block your account. See our process for dealing with violations for more details.