Confirmed users
241
edits
BMO: Difference between revisions
Jump to navigation
Jump to search
→Current Projects
No edit summary |
|||
| Line 20: | Line 20: | ||
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 | 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. | 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. | ||
<table style="width: 100%" class="fullwidth-table sortable" border="1"> | |||
<tr> | |||
<th>Description</th> | |||
<th>Goal</th> | |||
<th>Priority</th> | |||
<th>ETA</th> | |||
<th>Status</th> | |||
</tr> | |||
<tr> | |||
<td>[[BMO/40Upgrade|4.0 Upgrade]]</td> | |||
<td>b.m.o is currently running Bugzilla version 3.6 and work is being done to upgrade to version 4.0 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.0. A schedule as well as current issues and remaining tasks will be available on the project home page.</td> | |||
<td>1</td> | |||
<td>TBD</td> | |||
<td>IN PROGRESS</td> | |||
</tr> | |||
<tr> | |||
<td>[[BMO/REST|Native REST API]]</td> | |||
<td>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. | |||
<td>4</td> | |||
<td>TBD</td> | |||
<td>PENDING</td> | |||
</tr> | |||
<tr> | |||
<td>[[BMO/CodeReview|Code Review Integration with b.m.o]]</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.</td> | |||
<td>1</td> | |||
<td>TBD</td> | |||
<td>IN PROGRESS</td> | |||
</tr> | |||
<tr> | |||
<td>[[BMO/Pulese|Pulse Integration]]</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>TBD</td> | |||
<td>PENDING</td> | |||
</tr> | |||
<tr> | |||
<td>[[BMO/SecureBugMail|Secure BugMail]]</td> | |||
<td></td> | |||
<td>3</td> | |||
<td>TBD</td> | |||
<td>PENDING</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.</td> | |||
<td>4</td> | |||
<td>TBD</td> | |||
<td>PENDING</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 brnaches of development and not necessarily specific release versions.</td> | |||
<td>4</td> | |||
<td>TBD</td> | |||
<td>PENDING</td> | |||
</tr> | |||
</table> | |||
== Other News == | == Other News == | ||
News related to b.m.o. | News related to b.m.o. | ||