THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

So, we want to have a clearly defined set of priorities and actions to move forward on the QAC. I'm making this pretty aggressive, so let me know if you feel it's too much too soon. But this is a pretty small application and I think we can achieve this.

Week 1: June 29 - July 3

Goal: Get us off on a running start, demo the changes to the Q tab as a mockup only

• Get Blog post on Redesign up
• Get schedule finalized
• Complete RPC bugzilla backend refactoring
• Remove the "platform" tabs - just make them a normal tab control
• Ask around about bugzilla account creation from RPC interface, see if anyone has any ideas
• General UI touchup off the bat

Week 2: July 6 - July 10

Goal: Implement Q tab, show off Bugzilla mockup.

• Implementation of Q tab
• Begin wiring bugzilla UI controller to bugzilla backend RPC/XHR library
• Begin working on Litmus tab redesign

Week 3: July 13 - July 17

Goal: Wire in bugzilla tab (probably have to ask user for credentials), show off litmus mockup

• Show off litmus tab mockup at design lunch on July 18
• Finish bugzilla work
• Begin the start up experience work, removing extraneous tabs, moving settings to preferences window
  • For version 1 we will only create a litmus and QMO account for new users, we'll punt on the bugzilla account creation due to limitations in the RPC interface.
• Implement the help link

Week 4: July 20 - July 24

Goal: Bring application together, polish any bugs, triage old bugs

• Triage old bugs to see which ones still apply, find and fix those, close ones that no longer apply as invalid.
• Polish UI
• Ask for review on UI and structure

Week 5: July 27 - July 31

Goal: Bug fix & release

• Fix any outstanding bugs
• Release to AMO.

Things to figure out

• How best to wire in the automatic querying so that it is responsive inside bugzilla
• How to implement the OS/platform detection code so that it isn't hard coded in litmus.js and so that we don't have to change it each time a new release comes out. Can we keep a file of known releases somewhere that we could XHR down and get them that way? Could we ask litmus for that info?
• Can we shorten the schedule?
• How and when do we port this to fennec?