Auto-tools/Projects/Bugzilla 2013Q2: Difference between revisions
| Line 7: | Line 7: | ||
= Milestones = | = Milestones = | ||
By the end of the quarter, we want to update the code review UI on bugzilla to make it more modern and feature comparable with our competitors, complete and deploy the tracking flags optimization & migration, complete and deploy the native REST API optimization | By the end of the quarter, we want to update the code review UI on bugzilla to make it more modern and feature comparable with our competitors, complete and deploy the tracking flags optimization & migration, complete and deploy the native REST API optimization. | ||
The project name for these whiteboard flags is "bugzilla" | The project name for these whiteboard flags is "bugzilla". | ||
== Milestone 1 Tentative Dates: April 1 - April 12 == | == Milestone 1 Tentative Dates: April 1 - April 12 == | ||
Revision as of 21:47, 10 May 2013
Make bugzilla more user-centric and to improve the various workflows for the various roles.
Breakdown and End Game
Right now, bugzilla is a one-size fits all system. And so it does some workflows well, it does some things less well since it tries to treat all roles with the same set of functionality. We can improve use cases and workflows across the board by making Bugzilla more user centric (right now you can think of it as very bug centric). We want to highlight the different roles, and streamline the workflows for each one.
Since this is our first step in this direction there are a set of "enabling" changes we want to make to bugzilla to advance our ability to scale and perform so that we can be more innovative with the various roles and workflows we want to create.
Milestones
By the end of the quarter, we want to update the code review UI on bugzilla to make it more modern and feature comparable with our competitors, complete and deploy the tracking flags optimization & migration, complete and deploy the native REST API optimization.
The project name for these whiteboard flags is "bugzilla".
Milestone 1 Tentative Dates: April 1 - April 12
- [DONE] Release plan for user workflows.
- [DONE] Complete requirements for user-profile page.
- [MISSED] Complete first draft of explanatory text for user-profile page.
- [MISSED] Finish implementation of new-style tracking flags.
Milestone 2 Tentative Dates: April 15 - April 26
- (carry over) [DONE] Complete first draft of explanatory text for user-profile page.
- (carry over) [MISSED] Finish implementation of new-style tracking flags.
- [MISSED] Deploy new tracking flags feature alongside old tracking flags.
- [MISSED] Complete tracking-flags migration script.
- [DONE] Finish vagrant box.
Milestone 3 Tentative Dates: April 29 - May 10
- (carry over) [ON TRACK] Finish implementation of new-style tracking flags.
- (carry over) [ON TRACK] Deploy new tracking flags feature alongside old tracking flags.
- (carry over) [ON TRACK] Complete tracking-flags migration script.
- [AT RISK] Complete testing of tracking-flags migration script.
- [AT RISK] Fix splinter papercuts.
- [ON TRACK] Determine SQL queries for user-profiles page.
Milestone 4 Tentative Dates: May 13 - May 24
- Complete Native REST API implementation.
- Determine design for user-profile page.
- Determine design for user roles OR start work on new code-review tool, depending on whether we have a potential GSoC intern.
Milestone 5 Tentative Dates: May 27 - June 7
- Deploy Native REST API implementation to dev server for testing.
- Start implementation of user-profile page.
- Start implementation of architectural changes for user roles (IF not working on code-review tool).
Milestone 6 Tentative Dates: June 10 - June 21
- Deploy Native REST API to production.
- Perform tracking-flags migration with IT. (?)
- Finish implementation of architectural changes for user roles OR finish code-review-tool migration.
Milestone 7 Tentative Date: June 24 - June 28
- Finish user-profile page.
- Deploy architectural changes for user roles OR deploy new code-review tool.