Working with DrDump

Guidelines

OpenCover uses DrDump to capture crash reports from OpenCover when the host encounters a crash. DrDump is configured to automatically raise a Bug when the issue count hits 20 instances, this is a manual update from the 1000 that is initially assigned when the first defect for that version number is submitted.

###Raising a DrDump issue in GitHub

There are no webhooks from DrDump to integrate into GitHub so for now the guidance is this:

1. Create new issue in GitHub using the same DrDump title and copy the stack trace to the message body as a code block (preserves formatting)
2. Check the dumps to evaluate the number of unique users affected to gauge the severity e.g. 1-3 (low) 4-8 (medium) 9- (high)
3. Add additional labels such as 'bug', 'drdump' etc as appropriate
4. Add the issue to the next milestone
5. Once saved, copy the url of the issue and save it as the tag to the DrDump report
6. If you intend to work on the issue yourself, then assign it to yourself on both DrDump and GitHub.

###Completing a DrDump issue in GitHub

Once issue resolved and passed tests and built correctly in AppVeyor.

1. Check the issue is still associated with a milestone (this helps us build the release notes)
2. Close the issue in GitHub
3. Close the issue in DrDump using the build number from AppVeyor

###DrDump access

If you want to work on an unassigned DrDump issue and don't have access to DrDump just raise an issue and we'll invite you - you will need to supply us with an email address so think of a way to obfuscate it but still human readable. e.g. shaun(underscore)wilde(at)hotmail(dot)com