What happens to the extensions in the current stable once a new one is released?

Assuming there will soon be a new stable release of Slicer, we need to understand what happens to the previous (current) stable and its extensions?

My understanding is that the extensions for r29738 (current stable) will be frozen at whether the latest built extensions were for it at the time (as opposed to rebuilding it with new changes to the extension). Is that correct?

The reason I am asking, at this point we have to do a lot of slicer version checks to make sure SlicerMorph works correctly with the current stable and the preview due to major changes to Markups, subject hierarchy and other module. When the new release comes, we would like to remove these, and get rid off the code to support 4.11, as long as r29738 continues to function with its own last SlicerMorph build.

Your understanding is correct.


Will we need to resubmit a new pull request to add extensions to the new stable release or will they automatically be pulled from the preview release GitHub repository?

A new branch is made off of the latest master branch of the ExtensionsIndex where effectively the specification for Slicer Preview and Slicer Stable are the same at this time of branching. Documentation/Nightly/Developers/ReleaseProcess - Slicer Wiki

Developers will have to submit PRs to this new branch potentially if the Slicer preview becomes incompatible with the new Slicer stable requiring the extension to maintain a separate branch. For example some extensions have a 4.11 branch that is compatible with the 4.11 stable, but the master branch is compatible with the Slicer Preview.

1 Like