QA:Keywords & Status Whiteboard

In addition to the various components, target milestones, keywords and flags, the Camino project uses certain Status Whiteboard entries to help tag and manage bugs.

Keywords

For a list of approved keywords, see Bugzilla's "Describe Keywords". These keywords are used across the Mozilla project, and only these keywords can be entered in Bugzilla's keywords field.

Those commonly used (or found) in Camino are

• fixed (plus a Gecko milestone, e.g. fixed1.7, fixed1.8.0.2)

  The bug was fixed in time for a particular non-trunk Gecko milestone, e.g. for a branch security release

• verified (plus a Gecko milestone, e.g. verified1.7, verified1.8.0.2)

  The bug's fix was verified in time for a particular non-trunk Gecko milestone, e.g. for a branch security release

• access

  Bugs with accessibility implications but which don't belong in the Accessibility component

• checkin-needed

  Bug with requisite reviews waiting for someone with cvs access to commit; see the status whiteboard for additional information about the checkin requirements

  Needs Checkin query (populated manually from Reviewed query)

• crash
• dataloss
• hang
• helpwanted
• intl
• meta
• mlk
• perf
• polish
• privacy
• qawanted

  This is a good place to look if you want to do some triaging. Bugs that get qawanted generally need testing on different browsers, regression windows, or basic trouble-shooting with the reporter (Camino qawanted)

• regression

  Camino regressions

• smoketest
• stackwanted
• testcase

  The bug has a reduced testcase attached. This is a requirement that must be fulfilled before transferrring a bug to many Core components (e.g., Layout, Printing) in the NEW state, and is a good idea to have before transferring to those components in the UNCONFIRMED state.

  Ideally, all Camino bugs in the Page Layout and HTML Form Controls components should have testcases.

• topcrash (and variations)
• zt4newcrash

Status Whiteboard

Entries in the status whiteboard supplement the official Mozilla-wide keywords and help us track certain bugs.

The following are regularly used in Camino:

• [CLOSEME - date]

  These are bugs for which QA has been performed and further questions have been asked of the reporter without reply for 1-2 weeks. If there is no reply within the next week, the bug will be closed WORKSFORME on the next Sunday evening.

• dupeme, DUPEME

  A bug which a member of the development or QA team thinks is a duplicate of an existing Camino or Core bug but which the person cannot locate at the time

• [camino-2.0]

  These bugs were "fixed" for a given Camino release by a checkin to the Camino 2.0 branch for that release. This is primarily to differentiate fixes landed for cvs trunk from those landed (or not yet landed) on the CAMINO_2_0_BRANCH.

• [camino-1.5.1], [camino-1.5.2], [camino-1.5.3], [camino-1.5.4], [camino-1.5.5]

  These bugs were "fixed" for a given Camino release by a checkin to the Camino 1.5 branch for that release. This is primarily to differentiate fixes landed for 1.6 (the fixed1.8.1.x keywords) from those landed (or not yet landed) on the CAMINO_1_5_BRANCH.

• [camino-1.0], [camino-1.0.1], [camino-1.0.2], [camino-1.0.3], [camino-1.0.4], [camino-1.0.5]

  These bugs were "fixed" for a given Camino release by a checkin to the Camino mini-branch for that release and may not have landed (fixed) on the branch from which the mini-branch diverged.

• [good first bug]

  A good bug for a first-time Camino coder

• l10n

  A bug with localization impact (used in the period leading up to the l10n freeze for a release)

• [nib-only]

  This bug requires no code changes, only changes to a nib.

• [good thirdparty]

  This bug won't be fixed in Camino, but is a good opportunity for a third-party solution.

• [needs-radar]

  This bug deals with an OS bug for which a reduced testapp and a rdar:// bug need to be filed with Apple

• rdar://somenumber

  The rdar:// bug report filed with Apple.