ReleaseEngineering/Bugzilla/Whiteboard

From MozillaWiki
Jump to: navigation, search

Active whiteboard tags for RelEng

These are tags that RelEng adds to the Whiteboard field in bugzilla to help us search and group bugs better by area of effect/effort. Multiple tags can/should be used where appropriate.

  • tegra
    • bugs that affect tegra operations, status, or reporting
  • releng-internal
    • bugs that will improve/change our workflow and don't affect external infrastructure (usually these are enhancement bugs with no owner)
  • buildduty
    • quick machine setup issues, one-off developer requests, or ongoing problems that require monitoring
  • slaveduty
  • database
    • bugs requiring work on our databases (scheduler_db, status_db, other)
  • qa
    • improve the quality of our releng infrastructure
  • buildbot
    • issues pertaining specifically to buildbot code, maintenance, improvements
  • documentation
    • a process that needs documentation
  • ftp
    • issues with stage, or with file transfers in general
  • hardware
    • issue involves a physical machine (usually a mobile device or ix machine)
  • vm
    • issue involves a virtual machine (VM)
  • badslave?
    • used to flag issues, possibly intermittent, that may be related to the slave itself. The slave may require re-imaging.
  • try-server/tryserver
    • issues that affect the tryserver
  • talos
    • bugs related to talos
  • unittest
    • relates to reftests or unittests
  • automation
    • relates to our continuous integration setup: buildbot factories and such. Can also relate to release automation, but should be combined with the [releases] tag for specificity.
  • releases
    • affects our release process
  • bouncer
    • requires updates to bouncer
  • buildmasters
    • affects our build, scheduler, or test masters
  • buildslaves
    • affects our build or test slaves
  • capacity
    • affects our ability to meet the build/test throughput needs of developers
  • graphserver
    • requires changes to graphserver code, or SQL changes/insertions to the graphserver db
  • timeout
    • bug involves a timeout
  • mobile
    • bug affects mobile builds or devices
  • l10n
    • relates to localization (l10n) repacks
  • puppet
    • affects configuration management on Linux/Mac
  • opsi
    • affects configuration management on Windows
  • qt
    • involves the Qt application/UI framework
  • partner-repacks
    • affects the partner repack process
  • byob
    • affects the Build Your Own Browser process
  • signing
    • affects build/installer signing on Windows (and soon Mac)
  • reporting or buildapi
    • relates to reporting needs, e.g. buildapi/JSON feeds, end-to-end time reports, regression ranges, etc.
  • buildapi
  • staging
    • issue affects our staging environment
  • mozharness
    • issue involves mozharness
  • simple
    • issue is non-invasive and is a good candidate for a new employee, intern, or community member to tackle. Note: "simple" does not necessarily imply "quick."
  • tinderbox
    • issues that affect tinderbox or require changes to tinderbox server code. Note: we're generally past the point of propping up tinderbox. These bugs are strong candidates for WONTFIX.
  • autoland
    • Issues that deal with the Autoland system.

Deprecated

  • downtime
    • we should be using the needs-reconfig? and needs-treeclosure? flags now