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

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

2013-06-14T07:43:25Z

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

JChris.FillionR: Change originally contributed by Andriy Fedorov on the Nightly page

2012-12-07T14:04:56Z

Change originally contributed by Andriy Fedorov on the Nightly page

JChris.FillionR: Change originally contributed by Francois Budin on the Nightly page

2012-12-07T14:03:45Z

Change originally contributed by Francois Budin on the Nightly page

JChris.FillionR at 15:18, 9 November 2012

2012-11-09T15:18:31Z

UpdateBot: Nightly -> 4.2

2012-10-31T21:56:05Z

Nightly -> 4.2

New page

=Create a new extension and adding it to the extension index=
[https://github.com/Slicer/ExtensionsIndex/blob/master/README.md#readme See instructions on github]

==Obtain an API key to submit on the extension server==
[https://github.com/Slicer/ExtensionsIndex#setting-up-an-account-and-obtaining-an-api-key See instructions on github]

==Upload an extension in the experimental folder==
[https://github.com/Slicer/ExtensionsIndex#manual-build See instructions on github]

==Contribute an extension description file ==
* [https://github.com/Slicer/ExtensionsIndex#contributing See instructions on github]
* Consider also reading [https://github.com/Slicer/ExtensionsIndex/wiki/Extension-description-file Extension description file format]

=Requesting an extension version update=

{{note}} this procedure is still under discussion.

* Update the master branch of both your local clone and your online ExtensionsIndex fork
<pre>
git add upstream git://github.com/Slicer/ExtensionsIndex # Add reference to the authoritative ExtensionsIndex
git fetch upstream # Fetch change of the authoritative ExtensionsIndex
git checkout master # Checkout master
git reset --hard upstream/master # Reset your local master branch using the authoritative master
git push origin master # Update the master branch of your online fork
</pre>
* Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex
* Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake
* Commit the <YourExtensionName>.s4ext file to your cloned ExtensionIndex repository (provide a meaningful commit comment)
* Push modifications to your ExtensionIndex fork on github
* Submit a pull request to https://github.com/Slicer/ExtensionsIndex (provide a meaningful commit comment)

← Older revision		Revision as of 07:43, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	=Create a new extension and adding it to the extension index=		=Create a new extension and adding it to the extension index=
	[https://github.com/Slicer/ExtensionsIndex/blob/master/README.md#readme See instructions on github]		[https://github.com/Slicer/ExtensionsIndex/blob/master/README.md#readme See instructions on github]

@@ Line 24: / Line 24: @@
 * Update the master branch of both your local clone and your online ExtensionsIndex fork
 <pre>
-git add upstream git://github.com/Slicer/ExtensionsIndex   # Add reference to the authoritative ExtensionsIndex
+git remote add upstream git://github.com/Slicer/ExtensionsIndex   # Add reference to the authoritative ExtensionsIndex
-git fetch upstream                                         # Fetch change of the authoritative ExtensionsIndex
+git fetch upstream                                                # Fetch change of the authoritative ExtensionsIndex
-git checkout master                                        # Checkout master
+git checkout master                                               # Checkout master
-git reset --hard upstream/master                           # Reset your local master branch using the authoritative master
+git reset --hard upstream/master                                  # Reset your local master branch using the authoritative master
-git push origin master                                     # Update the master branch of your online fork
+git push origin master                                            # Update the master branch of your online fork
 </pre>
 * Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex
@@ Line 47: / Line 47: @@
 * Update the 4.2.0 branch of both your local clone and your online ExtensionsIndex fork
 <pre>
-git add upstream git://github.com/Slicer/ExtensionsIndex   # Add reference to the authoritative ExtensionsIndex
+git remote add upstream git://github.com/Slicer/ExtensionsIndex   # Add reference to the authoritative ExtensionsIndex
-git fetch upstream                                         # Fetch change of the authoritative ExtensionsIndex
+git fetch upstream                                                # Fetch change of the authoritative ExtensionsIndex
-git checkout 4.2.0                                         # Checkout 4.2.0
+git checkout 4.2.0                                                # Checkout 4.2.0
-git reset --hard upstream/4.2.0                            # Reset your local 4.2.0 branch using the authoritative 4.2.0
+git reset --hard upstream/4.2.0                                   # Reset your local 4.2.0 branch using the authoritative 4.2.0
-git push origin 4.2.0                                      # Update the 4.2.0 branch of your online fork
+git push origin 4.2.0                                             # Update the 4.2.0 branch of your online fork
 </pre>
 * Create a branch named update-<YourExtensionName>-4.2.0 in the clone of your forked ExtensionsIndex

@@ Line 35: / Line 35: @@
 </pre>
 * Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake
 * Commit the <YourExtensionName>.s4ext file to your cloned ExtensionIndex repository (provide a meaningful commit comment)
 * Push modifications to your ExtensionIndex fork on github
@@ Line 56: / Line 58: @@
 </pre>
 * Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake
 * Commit the <YourExtensionName>.s4ext file to your cloned ExtensionIndex repository (provide a meaningful commit comment)
 * Push modifications to your ExtensionIndex fork on github

@@ Line 12: / Line 12: @@
 * Consider also reading [https://github.com/Slicer/ExtensionsIndex/wiki/Extension-description-file Extension description file format]
-=Requesting an extension version update=
+= Requesting an extension version update {{updated}} =
-{{note}} this procedure is still under discussion.
+On your local fork, the idea is to create the following topic branches:
 * Update the master branch of both your local clone and your online ExtensionsIndex fork
@@ Line 25: / Line 31: @@
 </pre>
 * Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex
 * Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake
 * Commit the <YourExtensionName>.s4ext file to your cloned ExtensionIndex repository (provide a meaningful commit comment)
 * Push modifications to your ExtensionIndex fork on github
 * Submit a pull request to https://github.com/Slicer/ExtensionsIndex (provide a meaningful commit comment)