1,623
edits
PostCrash: Difference between revisions
m
→User email contact
No edit summary |
|||
| Line 44: | Line 44: | ||
After discussion (see chofmann's comments below for background), we think the best way to solve this is with a manual process rather than an automated one., something like the following: | After discussion (see chofmann's comments below for background), we think the best way to solve this is with a manual process rather than an automated one., something like the following: | ||
* During the release process, a | * During the release process, a QA team member should collect a set of bugs fixed in the release and match with crash signatures. | ||
* Socorro should provide the ability for an admin user to email the set of users who have submitted crashes matching a particular signature. | * Socorro should provide the ability for an admin user to email the set of users who have submitted crashes matching a particular signature. | ||
* | * A SUMO team member should be responsible for composing the actual email. Something along the lines of:<br/><br/>''On date X/Y/Z you submitted a crash report to Mozilla. Crashes with this signature were addressed in bug xyz which has been resolved in Firefox version A.B.C.'' | ||
Issues with regard to authenticity of email / phishing can be addressed by encouraging users to "visit mozilla.com and click on blah for more information" (taking a lead from Paypal/eBay here). We should in general make sure that emails come from a mozilla.com address and use whatever we have in place for email authentication. | Issues with regard to authenticity of email / phishing can be addressed by encouraging users to "visit mozilla.com and click on blah for more information" (taking a lead from Paypal/eBay here). We should in general make sure that emails come from a mozilla.com address and use whatever we have in place for email authentication. | ||