Difference between revisions of "Documentation/Nightly/Report a problem"
From Slicer Wiki
m |
m |
||
Line 7: | Line 7: | ||
* 3. Create an issue in the [http://na-mic.org/Mantis/bug_report_page.php tracker]. For example, see issue [http://na-mic.org/Mantis/view.php?id=1906 #1906] | * 3. Create an issue in the [http://na-mic.org/Mantis/bug_report_page.php tracker]. For example, see issue [http://na-mic.org/Mantis/view.php?id=1906 #1906] | ||
− | * 4. Send an email on the [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel slicer-developers] list pointing to the reported bug. Title of the email should start with <code>[BUG <IssueNumber>] Title of the bug</code> | + | * 4. Optionally, if you would like to share dataset >= 2MB, you should consider uploading them on our dedicated server. See [[Documentation/{{documentation/version}}/Report_a_problem/UploadData|How to share and associate data with an issue]] |
+ | |||
+ | * 5. Send an email on the [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel slicer-developers] list pointing to the reported bug. Title of the email should start with <code>[BUG <IssueNumber>] Title of the bug</code> | ||
{{:Documentation/{{documentation/version}}/Developers/IssueWorkflow}} | {{:Documentation/{{documentation/version}}/Developers/IssueWorkflow}} |
Revision as of 20:44, 23 January 2013
Home < Documentation < Nightly < Report a problemThe following instructions describes the recommended workflow to report a problem related to Slicer application.
- 1. Register on the issue tracker
- 2. Sign-up on the developers mailing list
- 4. Optionally, if you would like to share dataset >= 2MB, you should consider uploading them on our dedicated server. See How to share and associate data with an issue
- 5. Send an email on the slicer-developers list pointing to the reported bug. Title of the email should start with
[BUG <IssueNumber>] Title of the bug
The following diagram illustrates Slicer issue workflow:
Source: Adapted from http://www.warelab.org/blog/?p=24