BMO: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 72: Line 72:
   <td>TBD</td>
   <td>TBD</td>
   <td>PENDING</td>
   <td>PENDING</td>
</tr>
<tr>
  <td>[[BMO/CodeReview|Code Review Integration]]</td>
  <td>Developers would like to improve the current code review process by integrating either Review Board or Splinter with b.m.o so that code review can be done directly from the bug report instead of entering a separate tool (https://bugzilla.mozilla.org/show_bug.cgi?id=570786).</td>
  <td>1</td>
  <td>Splinter Released with 4.0</td>
  <td>COMPLETED</td>
</tr>
</tr>
<tr>
<tr>
Line 87: Line 80:
   <td>TBD</td>
   <td>TBD</td>
   <td>PENDING</td>
   <td>PENDING</td>
</tr>
<tr>
  <td>[[BMO/SecureBugMail|Secure BugMail]]</td>
  <td>Need a way to be able to interact with Bugzilla in a secure way so that changes made to bug reports or new bugs submitted can be guaranteed that they came from the proper person. Two possible solutions to this is the use of one time use tokens and/or GPG encryption.</td>
  <td>2</td>
  <td>Released with 4.0</td>
  <td>IN PROGRESS (Waiting to turn on for specific groups)</td>
</tr>
<tr>
  <td>[[BMO/ComponentWatch|Component Watching]]</td>
  <td>Currently b.m.o only allows for watching for particular user accounts. Users of b.m.o would like to also be able to receive bug notifications on bugs assigned specific Bugzilla field values such as component, version, etc (https://bugzilla.mozilla.org/show_bug.cgi?id=634531).</td>
  <td>4</td>
  <td>Released with 4.0</td>
  <td>COMPLETED</td>
</tr>
<tr> 
  <td>[[BMO/BranchStatus|Branch Status Support]]</td>
  <td>b.m.o needs a better way to handle bug reports that are for specific branches of development and not necessarily specific release versions (https://bugzilla.mozilla.org/show_bug.cgi?id=55970).</td>
  <td>4</td>
  <td>TBD</td>
  <td>PENDING</td>
</tr>
<tr>
  <td>[[BMO/Sitemap|Sitemap Extension]]</td>
  <td>Allow various search engines to index bugs in b.m.o (https://bugzilla.mozilla.org/show_bug.cgi?id=223988)</td>
  <td>4</td>
  <td>Released with 4.0</td>
  <td>COMPLETED</td>
</tr>
<tr>
  <td>[[BMO/InlineHistory|Inline History]]</td>
  <td>Move all bug activity/history onto the main bug page.  (https://bugzilla.mozilla.org/show_bug.cgi?id=492674 and https://bugzilla.mozilla.org/show_bug.cgi?id=11368).</td>
  <td>4</td>
  <td>Released</td>
  <td>COMPLETED</td>
</tr>
</tr>
</table>
</table>

Revision as of 16:18, 14 May 2012

Bugzilla@Mozilla

This is the main public page for all things related to https://bugzilla.mozilla.org (b.m.o). 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.

Contributors/Maintainers

  • dkl: Dave Lawrence (Owner/Engineer)
  • glob: Byron Jones (Owner/Engineer)
  • justdave: Dave Miller (Admin)
  • gerv: Gervase Markham (Grease Gun)
  • reed: Reed Loden (Engineer/Admin [Volunteer])

Bugzilla Tips and Other Useful Documentation

Information About BMO

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.

Administrative Procedures

Meeting Information

Every Monday 8:30 AM PT, Vidyo Room of Byron Jones (479), Dial-in extension 90479.

Current Projects

Here is a table of current projects being worked on for the near future. These are larger scale projects and not related to day to day bug fixing and features reported in individual bug reports. They will be prioritized and a schedule will be assigned based on current resources available. Click on the project description to get more detailed information.

Description Goal Priority ETA Status
4.2 Upgrade b.m.o is currently running Bugzilla version 4.0 and work is being done to upgrade to version 4.2 once the upstream community releases it. This keeps b.m.o updated with all of the recent bug fixes and well as new features available in 4.2. A schedule as well as current issues and remaining tasks will be available on the project home page. 1 TBD PENDING
Tracking Flags b.m.o is currently utilizing custom fields to aid in tracking releases for Firefox, Thunderbird, and other projects. This is not ideal as every release requires even more custom fields to be created causing certain tables in Bugzilla to grow very large in number of columns. This new TrackingFlags extension will move the fields to their own tables which will allow us to continue to grow without affecting the core Bugzilla tables and also hopefully improve performance as a result. 1 TBD PENDING
Native REST API (see also Bugzilla:REST_API) Thanks to work done by Gervase, b.m.o has had a full featured REST API available to Bugzilla user's for some time now. Currently the REST API sits on a separate proxy between the client and the b.m.o server. Eventually we would like to see this become part of the core Bugzilla API. 4 TBD PENDING
Pulse Integration This extension sends messages to a message broker via AMQP or STOMP whenever an object (bug, keyword, component, etc) is created or modified (https://bugzilla.mozilla.org/show_bug.cgi?id=589322). 2 TBD PENDING

Past Projects

Other News

News related to b.m.o.