Difference between revisions of "Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions"

From Slicer Wiki
Jump to: navigation, search
Line 16: Line 16:
 
On your local fork, the idea is to create the following topic branches:
 
On your local fork, the idea is to create the following topic branches:
 
* <code>update-<YourExtensionName></code> based of [https://github.com/Slicer/ExtensionsIndex/tree/master <code>master</code>] integration branch.
 
* <code>update-<YourExtensionName></code> based of [https://github.com/Slicer/ExtensionsIndex/tree/master <code>master</code>] integration branch.
* <code>update-<YourExtensionName>-4.2.0</code> based of [https://github.com/Slicer/ExtensionsIndex/tree/4.2.0 <code>4.2.0</code>] integration branch.
+
* <code>update-<YourExtensionName>-4.2</code> based of [https://github.com/Slicer/ExtensionsIndex/tree/4.2 <code>4.2</code>] integration branch.
  
  
Line 47: Line 47:
 
The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk.
 
The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk.
  
* Update the 4.2.0 branch of both your local clone and your online ExtensionsIndex fork
+
* Update the 4.2 branch of both your local clone and your online ExtensionsIndex fork
 
<pre>
 
<pre>
 
git remote 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                                                 # Checkout 4.2
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                                     # Reset your local 4.2 branch using the authoritative 4.2
git push origin 4.2.0                                            # Update the 4.2.0 branch of your online fork
+
git push origin 4.2                                               # Update the 4.2 branch of your online fork
 
</pre>
 
</pre>
* Create a branch named update-<YourExtensionName>-4.2.0 in the clone of your forked ExtensionsIndex
+
* Create a branch named update-<YourExtensionName>-4.2 in the clone of your forked ExtensionsIndex
 
<pre>
 
<pre>
git checkout -b update-<YourExtensionName>-4.2.0
+
git checkout -b update-<YourExtensionName>-4.2
 
</pre>
 
</pre>
 
* Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake
 
* Regenerate the <YourExtensionName>.s4ext file by configuring your extension with CMake

Revision as of 20:44, 4 February 2013

Home < Documentation < Nightly < Developers < Tutorials < BuildTestPackageDistributeExtensions

Create a new extension and adding it to the extension index

See instructions on github

Obtain an API key to submit on the extension server

See instructions on github

Upload an extension in the experimental folder

See instructions on github

Contribute an extension description file

Requesting an extension version update

On your local fork, the idea is to create the following topic branches:

  • update-<YourExtensionName> based of master integration branch.
  • update-<YourExtensionName>-4.2 based of 4.2 integration branch.


Extensions build against Slicer trunk

The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk.

  • Update the master branch of both your local clone and your online ExtensionsIndex fork
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 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
  • Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex
git checkout -b update-<YourExtensionName>


Extensions build against Slicer 4.10

The following instruction describes how to contribute extension description file updates for an extension being built against slicer trunk.

  • Update the 4.2 branch of both your local clone and your online ExtensionsIndex fork
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 checkout 4.2                                                  # Checkout 4.2
git reset --hard upstream/4.2                                     # Reset your local 4.2 branch using the authoritative 4.2
git push origin 4.2                                               # Update the 4.2 branch of your online fork
  • Create a branch named update-<YourExtensionName>-4.2 in the clone of your forked ExtensionsIndex
git checkout -b update-<YourExtensionName>-4.2