It is fine if we either mention 5.12.1 version in the initial post or add a follow-up post in the same topic. But we probably don’t want people to download Slicer-5.12.0 for macOS (because loadable modules in extensions are not fixed up correctly in that version).
How about just a “Known issues” section of the announcement detailing the specific case of certain macOS extensions not working? That way the post about Slicer 5.12.0 can benefit the Windows and Linux users as well as any macOS users using Slicer core without any of the problematic extensions?
We would already want to indicate clearly to the community about why they should use 5.12.1 over 5.12.0 in certain situations. This would be a 5.12.1 release notes type mention.
Planning to post the 5.12.0 release announcement around the same time as a 5.12.1 release, for the sake of making something available for macOS users that works with C++ extensions. The linux and windows nightly don’t need to be paused for 5.12.1 because we can just rebuild the existing stable; the macOS needs to rebuild extnesions as well so we may need to pause the nightly for 5.12.1.
Wiki
The failures seem to be a resource issue, because the pages randomly load or fail at different times.
It’s hosted on digitalocean. Sam might be able to access the system to look into adding resources.
We should migrate the wiki to something else eventually: slicer core docs for slicer aspects, and we’ll need to come up with something for extension docs – maybe a dedicated extension docs archive repo or github wiki page.
Sam accessed the system dashboard: it seems to be a storage issue. Creating a backup snapshot and then attempting to increase storage…
NNInteractive pip install threading issue
It should be possible to add a failsafe in Slicer, Ebrahim looking into doing that before 5.12.1 if it is a small change.