Difference between revisions of "Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions"
From Slicer Wiki
Line 38: | Line 38: | ||
− | The above instruction can easily be adapted to push updates associated with <code>update-<YourExtensionName>-4.2.0</code> by using <code>4.2.0</code> instead of <code>master</code> | + | {{note}} The above instruction can easily be adapted to push updates associated with <code>update-<YourExtensionName>-4.2.0</code> by using <code>4.2.0</code> instead of <code>master</code> |
Revision as of 14:15, 9 November 2012
Home < Documentation < Nightly < Developers < Tutorials < BuildTestPackageDistributeExtensionsContents
Create a new extension and adding it to the extension index
Obtain an API key to submit on the extension server
Upload an extension in the experimental folder
Contribute an extension description file
- See instructions on github
- Consider also reading Extension description file format
Requesting an extension version update UPDATED
On your local fork, the idea is to create the following topic branches:
update-<YourExtensionName>
based ofmaster
integration branch.update-<YourExtensionName>-4.2.0
based of4.2.0
integration branch.
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 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>
- 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)
The above instruction can easily be adapted to push updates associated with update-<YourExtensionName>-4.2.0
by using 4.2.0
instead of master