I am going to focus on these side projects in the coming weeks, in addition to driving the Firefox security releases. If you see anything missing or something that needs my attention, please let me know.
Projects in order of importance
- Patch for Bugzilla to add rich bug relations.
This will give us greater confidence that bugs aren’t missed/overlooked. It will also help development by organizing bugs consistently and allow for richer tools, processes, and progress reporting
- Create a new “release management” system that will manage all aspects of a release.
This will allow consistent processes between different teams/releases, make sure nothing is missed, add checking tools, and generally become the “truth” when it comes to release metadata (schedule, state, status, etc)
- Get Mozilla Pulse (http://pulse.mozilla.org) solid, usable, and useful.
Pulse has the opportunity to make all systems at Mozilla better. I hit some bumps with RabbitMQ but will be working on ironing them out and providing a scalable, HA system that can later be handed over to another team
- Create a triage reporting tool.
This will make the approval processes more open by publishing triage notes and results. It will also be a place to put action items so that they are acted upon before the next triage session
- Finish new release note framework.
I started this when I first came but got tied up in other projects. The way we do release notes involves a lot of copy and paste, it is difficult for QA to create automated tests, etc. I intend to fix this
- Patch for TabCandy to support user-defined rules.
The response to TabCandy has been great, but I think having this feature will be essential for power users and those who don’t want to manually organize tab groups. I’ve looked at the TabCandy code a bit and this shouldn’t be too hard to hack in. I may work on this a bit as a breather from the above projects (but probably not)
If you have any ideas about these systems (or others you think release management needs), please let me know!