Mailing list for QA and Reviewers

Bug #795689 reported by Dave Morley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Developer registration portal
Fix Released
Low
Danny Tamez

Bug Description

Bug Description:
Pretty soon the current method will be unmanageable. We need a mailing lis in place to alert reviews and then qa to the existence of an application in their relative queues.

This will then allow a user in those teams to leap into action and deal with their part of the work.

Processing should be triggered for Review upon click send for review
Processing should be triggered for QA once the review is complete and is forwarded to QA

Version:
OS:
64bit Natty

Browser:
FF 4.0

Problem URL:
n/a

Steps To Reproduce:
1. Currently the process is iamfuzz gets the package off the dev then asks the dev to fill out the form while he and I wait for him to complete
2. This is not a practical solution once we are out of beta

Expected Result:
I expect a nice mail saying there is something pending review/qa to land in my inbox so it can be dealt with.

tags: added: kb-improvement sp-1
Changed in developer-portal:
importance: Undecided → Low
Changed in developer-portal:
assignee: nobody → Danny Tamez (zematynnad)
Changed in developer-portal:
status: New → In Progress
Revision history for this message
Michael Nelson (michael.nelson) wrote :

bug 797099 might be a potential drive-by fix for this branch too... see what you think.

Changed in developer-portal:
status: In Progress → Fix Committed
Revision history for this message
Dave Morley (davmor2) wrote :

Mich

Revision history for this message
Dave Morley (davmor2) wrote :

Michael that might be a partial fix.

What I would like though is to not have to log in hourly to see if a developer has added a new application since I last logged in.

The mailing list approach would mean the list got mailed when an app was ready for the different stages and then I know to login

Revision history for this message
Michael Nelson (michael.nelson) wrote :

Hey Dave. Just to clarify, I wasn't suggesting any direction for this bug itself, just pointing out that while fixing this bug, it might be a chance to fix 797099 at the same time (and I didn't work on it :)).

Changed in developer-portal:
milestone: none → 11.06
Changed in developer-portal:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.