Difference between revisions of "Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions"
From Slicer Wiki
(4.1 -> Nightly) |
|||
Line 13: | Line 13: | ||
=Requesting an extension version update= | =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 | * Create a branch named update-<YourExtensionName> in the clone of your forked ExtensionsIndex | ||
* 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 14:04, 15 October 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
Requesting an extension version update
this procedure is still under discussion.
- 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
- 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)