# 2026.07.07 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2026-07-07-weekly-meeting/47523>\
**Category:** Weekly meetings\
**Created:** [July 1, 2026, 3:43pm UTC](https://discourse.slicer.org/t/2026-07-07-weekly-meeting/47523 "2026-07-01T15:43:43Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![ebrahim](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ebrahim/32/13403_2.png) [@ebrahim](https://discourse.slicer.org/u/ebrahim)\
**Post date:** [July 7, 2026, 4:13pm UTC](https://discourse.slicer.org/t/2026-07-07-weekly-meeting/47523/9 "2026-07-07T16:13:40Z")

</div>

Notes from meeting

## Agenda

- finalizing of release announcement which we are planning to post at the end of Wednesday
- [future of the wiki](https://discourse.slicer.org/t/slicer-wiki-appears-to-be-down/47528/2)
- [whether a patch release is in order for the macOS C++ extension issues](https://discourse.slicer.org/t/c-extension-for-5-12-is-not-working-macos/47542).
- [Nninteractive (slicer client) is stuck](https://discourse.slicer.org/t/nninteractive-slicer-client-is-stuck/47550/7)

## Releases

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.

> <https://github.com/Slicer/Slicer/issues/9271>
>
> \_Based on the state of the relevant sub-tasks, consider updating the issue descr…iption changing \`:question:\` (:question:) into either \`:hourglass\_flowing\_sand:\` (:hourglass\_flowing\_sand:) or \`:heavy\_check\_mark:\` (:heavy\_check\_mark:).\_
> 
> \--------------------------------------
> 
> Checklist \*\*Installers Release\*\*:
> 
> \* \[\] \[Pin\](https://docs.github.com/en/enterprise-cloud@latest/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository) this issue.
> \* \[\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-release-in-progress-post) the \`Release in progress\` post.
> \* \[\] \[Disable\](https://github.com/Slicer/Slicer/wiki/Release-Process#enable-or-disable-regular-nightly-builds) regular nightly builds.
> \* \[\] \`CMakeLists.txt\`: \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#cmakeliststxt-update-the-slicer-version-information-for-the-release) the Slicer version information for the release.
> \* \[\] \[Tag\](https://github.com/Slicer/Slicer/wiki/Release-Process#tag-the-repository) the repository with \`v5.12.1\`.
> \* \[\] \[Create\](https://github.com/Slicer/Slicer/wiki/Release-Process#create-release-or-patch-release-on-slicer-packageskitwarecom) release \`5.12.1\` on \[slicer-packages.kitware.com\](https://slicer-packages.kitware.com/#folder/5f4474d0e1d8c75dfc705482).
> \* \[\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-release-scripts) release scripts.
> \* \[\] \[Generate\](https://github.com/Slicer/Slicer/wiki/Release-Process#generate-application-and-extension-packages) application and extension packages. See https://slicer.cdash.org/index.php?project=SlicerStable&date=YYYY-MM-DD.
> \* Linux: :question:
> \* macOS: :question:
> \* Windows: :question:
> \* \[\] Update \[Release Details\](https://github.com/Slicer/Slicer/wiki/Release-Details) on the Slicer GitHub wiki.
> 
> \--------------------------------------
> 
> Checklist \*\*Post Release\*\*:
> 
> \_These steps will take place in the week following \*\*Installers Release\*\* steps\_
> 
> \* \[\] \[Re-enable\](https://github.com/Slicer/Slicer/wiki/Release-Process#enable-or-disable-regular-nightly-builds) regular nightly builds.
> \* \[\] Manually \[sign the packages\](https://github.com/Slicer/Slicer/wiki/Signing-Application-Packages).
> \* Linux: NA
> \* macOS: signed :question:, notarized :question:
> \* Windows: :question:
> \* \[\] \[Upload\](https://github.com/Slicer/Slicer/wiki/Release-Process#upload-signed-release-packages) signed release packages in the release folder.
> \* Linux: NA
> \* macOS: :question:
> \* Windows: :question:
> \* \[\] In the \`5.12.1\` release folder, update each \`Slicer\_\<os\>\_\<arch\>\_\<revision\>\` items changing the \`pre\_release\` metadata from \`true\` to \`false\`.
> \* Linux: :question:
> \* macOS: :question:
> \* Windows: :question:
> \* \[\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-extensionstats-module) \`ExtensionStats\` module.
> \* \[\] \[Update\](https://github.com/Slicer/Slicer/wiki/Release-Process#update-external-websites) external websites.
> \* \[\] \[Generate release notes\](https://github.com/Slicer/Slicer/wiki/Generating-Release-Notes) and prepare Discourse content.
> \* \[\] Finalize Slicer Announcement and release notes in HackMD (or equivalent shared document).
> \* \[\] Publish Slicer Announcement & release notes on Discourse.
> \* \[\] Unpin this issue.

## 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.

---

_[View the full topic](https://discourse.slicer.org/t/2026-07-07-weekly-meeting/47523)._