Difference between revisions of "Documentation/4.2/Report a problem"
From Slicer Wiki
m (Thanks Julien Finet) |
(Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | <noinclude>{{documentation/versioncheck}}</noinclude> | ||
The following instructions describes the recommended workflow to report a problem related to Slicer application. | The following instructions describes the recommended workflow to report a problem related to Slicer application. | ||
| Line 9: | Line 10: | ||
* 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. 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}} | |
| − | |||
Latest revision as of 07:41, 14 June 2013
Home < Documentation < 4.2 < Report a problem
|
For the latest Slicer documentation, visit the read-the-docs. |
The 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. 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
Mantis workflow
The following diagram illustrates Slicer issue workflow:
Source: Adapted from http://www.warelab.org/blog/?p=24
