Documentation/4.2/Developers/Tutorials/ContributePatch - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:41:57Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

JChris.FillionR: Undo revision 32158 by JChris.FillionR (Talk)

2013-06-14T06:10:03Z

Undo revision 32158 by JChris.FillionR (Talk)

JChris.FillionR at 06:09, 14 June 2013

2013-06-14T06:09:44Z

JChris.FillionR at 20:32, 9 November 2012

2012-11-09T20:32:24Z

UpdateBot: Nightly -> 4.2

2012-10-31T21:58:55Z

Nightly -> 4.2

New page

The following instructions describes the recommended workflow to contribute patch to Slicer code base.

It is also assumed you followed the [[Documentation/4.1/Developers/StartHere#New_community_member_checklist|New community member checklist]] and have a clone of https://github.com/Slicer/Slicer/.

'''If not already done, make sure to read the [[Documentation/{{documentation/version}}/Developers/Style_Guide|Slicer Coding Style Guide]] :-)'''

* 1. 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]

* 2. Make sure your fork has a [https://help.github.com/articles/adding-a-remote git remote]. Replace <code>jcfr</code> with your git login.
<pre>
git remote add jcfr git@github.com:jcfr/Slicer.git
</pre>

* 3. Create a topic named <code><issuer_number>-a-descriptive-topic-name</code>. For example:
<pre>
git checkout -b 1906-uninstall-extensions-on-restart
</pre>

* 4. Add a note to the issue with a link pointing to your topic. For example, see note [http://na-mic.org/Mantis/view.php?id=1906#c4578 1906#c4578]

* 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 - <category></code>

← Older revision		Revision as of 07:41, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	The following instructions describes the recommended workflow to contribute patch to Slicer code base.		The following instructions describes the recommended workflow to contribute patch to Slicer code base.

← Older revision		Revision as of 06:10, 14 June 2013
Line 1:		Line 1:
−	~~<noinclude>{{documentation/versioncheck}}</noinclude>~~
	The following instructions describes the recommended workflow to contribute patch to Slicer code base.		The following instructions describes the recommended workflow to contribute patch to Slicer code base.

← Older revision		Revision as of 06:09, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	The following instructions describes the recommended workflow to contribute patch to Slicer code base.		The following instructions describes the recommended workflow to contribute patch to Slicer code base.

← Older revision		Revision as of 20:32, 9 November 2012
Line 20:		Line 20:

	* 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 - <category></code>		* 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 - <category></code>
		+
		+	{{:Documentation/{{documentation/version}}/Developers/IssueWorkflow}}