This is the main public page for all things related to https://bugzilla.mozilla.org, aka b.m.o, Mozilla's customized version of Bugzilla. Here you can find information such as who is actively maintaining and contributing to b.m.o and what tasks are currently being worked on. Other information such as recent meeting minutes, and current release schedules can also be found here.
- dkl: Dave Lawrence (Owner/Engineer)
- glob: Byron Jones (Owner/Engineer)
- mcote: Mark Côté (Overseer/Dark Lord)
- justdave: Dave Miller (Admin)
- gerv: Gervase Markham (Grease Gun)
- reed: Reed Loden (Engineer/Admin [Volunteer])
- lizzard: Liz Henry (Bugmaster)
Bugzilla Tips and Other Useful Documentation
- BMO Tips (Webdev)
- Bugzilla for Humans
- Setting up your own BMO development environment
- Best practices and etiquette for integrating external apps with BMO
Information About BMO
- Discussion forum is mozilla.tools.bmo [mailing list] [Google Group] [USENET]
- Frequently Asked Questions
- Requesting Changes to BMO
- BMO Hardware Diagram
- Hacking on BMO
- Info and plans on Bugzilla's REST API and BMO-specific modifications/extensions
Policies and Procedures
- bugzilla.mozilla.org will receive normal code updates every Thursday at no specific time if changes need to be pushed out.
- Security fixes or other fatal type errors will always go out as soon as possible.
- Adding a new "rapid release" version
- Adding a new BMO security group
- Planning a BMO outage
- Restoring Disabled Accounts
- Retiring Products and Components Moving things to the Graveyard classification.
This table lists the bugs representing the current quarterly goals. Those that were set at the beginning of the quarter are tagged with the keyword "bmo-goal". The BMO team also regularly gets requests for high-priority work items throughout the quarter; those that will take more than a day or two in total, thus potentially jeopardizing other goals, are included below, tagged with "bmo-big". The daily smaller tasks are also generally tracked in Bugzilla but not represented in the table below.
P1 indicates a critical project. P2 indicates an important but deferrable item. P3 is as P2 but more deferrable. Note that all items are important, and it is presumed that lower-priority items will increase in priority over time as high-priority tasks are completed, i.e., we don't plan to defer any of these tasks indefinitely.
= $all-$resolved ?> Open; = $resolved ?> Resolved; = $all ?> Total (50% complete)
Further documentation about goals above and other projects follows:
- User Roles
- Generate different user roles based on what tasks a user is trying to complete when using the BMO system.
- Change Notification System
- Support for scalable push-based notifications of bug updates.
- Migrating Bugzilla and BMO code from bzr to git
Some of these will have on-going maintenance and improvements, but the initial deployment has been accomplished. Others have been abandoned or rejected due to various factors, noted below.
- 4.0 Upgrade
- 4.2 Upgrade (Completed March 5th, 2013)
- User Profiles
- Tracking Flags
- Native REST API
- Pulse Integration
- This was completed and deployed, but it generated a lot of traffic and is of questionable utility since it must access Bugzilla as an anonymous user. A simpler, more general system is the Change Notification System.
News related to b.m.o.