Documentation/Labs/EasyExtensionContribution - Revision history

JChris.FillionR: Undo revision 37377 by JChris.FillionR (Talk)

2014-02-27T17:46:41Z

Undo revision 37377 by JChris.FillionR (Talk)

JChris.FillionR at 17:45, 27 February 2014

2014-02-27T17:45:31Z

JChris.FillionR at 21:31, 5 December 2013

2013-12-05T21:31:19Z

JChris.FillionR: Created page with 'The current process to contribute a new or updated extension description file (*.s4ext) is documented [[Documentat…'

2013-12-05T21:31:04Z

Created page with 'The current process to contribute a new or updated extension description file (*.s4ext) is documented [[Documentat…'

New page

The current process to contribute a new or updated [[Documentation/Nightly/Developers/Extensions/DescriptionFile|extension description file (*.s4ext)]] is documented [[Documentation/Nightly/Developers/Tutorials/Contribute_Extension_Description_File|here]].

We all agree it involves a lot of steps. To simplify this process, the idea would be to provide a set of git custom command automating most of it.

The proposed improvment would be:

1. Clone the ExtensionsIndex

2. Checkout either <code>master</code> or <code>4.3</code> branch

3. run <code>./Utilities/SetupForDevelopment.sh</code>

4. run this command:

git prepare-extension-update /path/to/description-file.s4ext

This would:
* locally create the topic "update-<ExtensionName>[-X.Y]" or "add-<ExtensionName>[-X.Y]"
* generate meaningful commit message if possible (for svn and git based repo)
* associate compare link if possible

5. Then, if everything look good:

git push-extension-update

This would publish the topic on your fork and submit the pull request

@@ Line 1: / Line 1: @@
-This page serves as roadmap for the Slicer Extensions project.
+We all agree it involves a lot of steps. To simplify this process, the idea would be to provide a set of git custom command automating most of it.
-=== In progress ===
+The proposed improvement would be:
-=== Done ===
+. Clone the ExtensionsIndex
-=== To be done ==
+. Checkout either <code>master</code> or <code>4.3</code> branch
-== Extension catalog ==
+. run <code>./Utilities/SetupForDevelopment.sh</code>
-=== In progress ===
+. run this command:
-=== Done ===
+    git prepare-extension-update /path/to/description-file.s4ext
-=== To be done ==
+This would:
-== Extension manager ==
+. Then, if everything look good:
-=== To be done ===
+   git push-extension-update
-−
+This would publish the topic on your fork and submit the pull request

@@ Line 1: / Line 1: @@
-We all agree it involves a lot of steps. To simplify this process, the idea would be to provide a set of git custom command automating most of it.
+This page serves as roadmap for the Slicer Extensions project.
-The proposed improvement would be:
+=== In progress ===
-. Clone the ExtensionsIndex
+=== Done ===
-. Checkout either <code>master</code> or <code>4.3</code> branch
+=== To be done ==
-. run <code>./Utilities/SetupForDevelopment.sh</code>
+== Extension catalog ==
-. run this command:
+=== In progress ===
-    git prepare-extension-update /path/to/description-file.s4ext
+=== Done ===
-This would:
+=== To be done ==
-. Then, if everything look good:
+== Extension manager ==
-   git push-extension-update
+=== To be done ===
-−
+*
-This would publish the topic on your fork and submit the pull request