Difference between revisions of "Documentation/Nightly/Create a feature request"
From Slicer Wiki
m |
(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 create a feature request related to Slicer application. | The following instructions describes the recommended workflow to create a feature request related to Slicer application. | ||
| Line 7: | Line 8: | ||
* 3. Create an issue in the [http://na-mic.org/Mantis/bug_report_page.php tracker]. | * 3. Create an issue in the [http://na-mic.org/Mantis/bug_report_page.php tracker]. | ||
| − | * 4. Send an email on the [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel slicer-developers] list pointing to the reported feature request. Title of the email should start with <code>[FEATURE | + | * 4. Send an email on the [http://massmail.bwh.harvard.edu/mailman/listinfo/slicer-devel slicer-developers] list pointing to the reported feature request. Title of the email should start with <code>[FEATURE IssueNumber] Title of the feature request</code> |
{{:Documentation/{{documentation/version}}/Developers/IssueWorkflow}} | {{:Documentation/{{documentation/version}}/Developers/IssueWorkflow}} | ||
Latest revision as of 07:51, 14 June 2013
Home < Documentation < Nightly < Create a feature request
|
For the latest Slicer documentation, visit the read-the-docs. |
The following instructions describes the recommended workflow to create a feature request related to Slicer application.
- 1. Register on the issue tracker
- 2. Sign-up on the developers mailing list
- 3. Create an issue in the tracker.
- 4. Send an email on the slicer-developers list pointing to the reported feature request. Title of the email should start with
[FEATURE IssueNumber] Title of the feature request
The following diagram illustrates Slicer issue workflow:
Source: Adapted from http://www.warelab.org/blog/?p=24
