Changes

** Enhanced emails stating what will probably happen next to their bug report and how to keep an eye on its progress. Maybe describing once a bug has been resolved, how tobest obtain a binary or new version that may contain the fix/enhancement.

** Reviewers will need a top quality review tool for managing patches within BMO that need their attention. Utilizing the Dashboard, the user could then see which patches tthey need to look at in order of importance. Then from the dashboard, go directly to the review tool where the user would be able to approve the patch, mark it up with comments and/or kick it back to the author to be revised. ** Currently BMO uses Splinter for reviewing patches. It is a goal of Q3 to update Splinter (or replace) to fix some of the outstanding issues with the tool. Splinter has iissues with parsing certain patches and needs to have the parsing part split away and handled by server side PatchReader. Also BMO devels are looking at replacing the overlying javascript code with codereview.js which has more features than Splinter and is more actively maintained by the Webkit community.

** Once a patch has been reviewed and is ready for further attention, the patch committer user can then post the patch to an automated build system for actual testing. Partof the plans for BMO are to better integrate with the Try system using AutoLand. This will allow the committer role to tag approved patches and have them picked up automatically by AutoLand for submission to Try. AutoLand will then update the bug with the results of the Try run showing if it was a success, or failure and direct the user what to do next.** AutoLand is currently unmaintained and part of Q3 goals are to 1) take over ownership, move it to maintained hardware and work to fix an issues still outstanding or 2) wwork with RelEng who have shown interest in helping out and figure out how to get the system up to speed.