Difference between revisions of "Documentation/4.2/Create a feature request"

From Slicer Wiki
Jump to: navigation, search
m (Created page with 'The following instructions describes the recommended workflow to create a feature request related to Slicer application. * 1. [http://na-mic.org/Mantis/signup_page.php Register…')
 
(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 8: Line 9:
  
 
* 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>
 
* 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}}

Latest revision as of 07:40, 14 June 2013

Home < Documentation < 4.2 < 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.

  • 2. Sign-up on the developers mailing list
  • 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


Mantis workflow

The following diagram illustrates Slicer issue workflow:

Mantis-workflow.png

Source: Adapted from http://www.warelab.org/blog/?p=24