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

From Slicer Wiki
Jump to: navigation, search
Line 8: Line 8:
 
[https://github.com/Slicer/ExtensionsIndex#manual-build See instructions on github]
 
[https://github.com/Slicer/ExtensionsIndex#manual-build See instructions on github]
  
==Contribute an extension description file==
+
==Contribute an extension description file ==
 
[https://github.com/Slicer/ExtensionsIndex#contributing See instructions on github]
 
[https://github.com/Slicer/ExtensionsIndex#contributing See instructions on github]
  
 
=Requesting an extension version update=
 
=Requesting an extension version update=
 +
 +
Note: this procedure is still under discussion.
 +
 
Prepare an update repository/branch
 
Prepare an update repository/branch
 
* 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

Revision as of 20:58, 9 August 2012

Home < Documentation < 4.1 < 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

See instructions on github

Requesting an extension version update

Note: this procedure is still under discussion.

Prepare an update repository/branch

  • 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)