PostCrash: Difference between revisions

839 bytes added ,  9 August 2010
(privacy concerns)
Line 44: Line 44:
This would in part be a manual workflow:
This would in part be a manual workflow:
# A Firefox bug is fixed in Bugzilla.
# A Firefox bug is fixed in Bugzilla.
# A cron job notices when a bug associated with a crash signature is fixed, and puts it in a queue for the QA team.
# A cron job notices when a bug associated with a crash signature is fixed, and puts it in a queue for the QA team.
# The QA team maintains this list of fixed signatures and keeps track of which Firefox release a fix is targeted for.
# The QA team maintains this list of fixed signatures and keeps track of which Firefox release a fix is targeted for.
# When a fix is scheduled for a final Firefox release, the QA team passes over a list of crash bugs fixed to the SUMO team.
# When a fix is scheduled for a final Firefox release, the QA team passes over a list of crash bugs fixed to the SUMO team.
Line 50: Line 50:
# The messages are sent to each user who submitted a crash report with that crash signature.
# The messages are sent to each user who submitted a crash report with that crash signature.
# The item is removed from the QA queue.
# The item is removed from the QA queue.
===Suggested alternate workflow===
(Laura) I think it's better to drive this from the Bugzilla end, as follows, as it's less work and hence more achievable in the time frame:
# When a release is planned generate a list of fixed bugs (from Bugzilla)
# Provide facility in Socorro to search by Bugzilla bug for a list of associated crashes
# For each associated crash, generate a list of user submitted emails (minus any users who have said they don't want to be emailed again) - this function should be available only from the admin interface
# Mark those emails as contacted for that given crash, so we don't contact them again.
Do we want to provide functionality to email these users in Socorro?  This feels like it belongs in a different system. Providing Support with a list of emails per crash bug should be enough for version 1.


= Secondary goals (not essential for this project) =
= Secondary goals (not essential for this project) =
1,107

edits