I noticed that many of the extensions in the ExtensionsIndex
4.8 branch are using
master for the extension repo. I initially thought I missed this, but it applies to many popular extensions. This is a big issue considering the breaking changes in Slicer post-4.8.
I am assuming the 4.8 branch was just forked from the master of ExtensionsIndex? Should we establish a process to automatically update all references to
master to the latest hash at the time ExtensionsIndex release branch is forked, or at least ask the extensions developers to update the index files?
Problem is, right now it is not straightforward to find the latest hash that was working and was tested against 4.8 branch of Slicer.