# Release of Slicer 5.0 in progress: Regular builds are disabled

**URL:** <https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187>\
**Category:** Development\
**Tags:** release-process\
**Created:** [April 28, 2022, 8:37pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187 "2022-04-28T20:37:59Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 28, 2022, 8:37pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/1 "2022-04-28T20:37:59Z")

</div>

This evening, regular preview and stable builds of Slicer and associated extensions will be disabled in favor of a new stable release.

To track the progress, see [Release Slicer v5.0 · Issue #6337 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/issues/6337)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 30, 2022, 5:51am UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/2 "2022-04-30T05:51:24Z")

</div>

Updates:

- Release has been tagged and packages are being generated. See dashboard [here](https://slicer.cdash.org/index.php?project=SlicerStable&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=)
- Regular will be resumed tomorrow

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 30, 2022, 8:18pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/3 "2022-04-30T20:18:58Z")

</div>

Updates:

- Last night build all complete along with the built of all extensions, that said a glitch related to toggling memory leaks that is specific to Stable build was identified (See issue [#6344](https://github.com/Slicer/Slicer/issues/6344)).

- This means that a maintenance branch will be created and **new tag called `v5.0.1`** will be published and associated release build will be **triggered tonight** (in place of our usual preview build).

### What about revisions

To ensure revision of potential patch release and on-going development associated with `5.1.0` would compare nicely, we pre-allocated 100 revisions (See [PR #6343](https://github.com/Slicer/Slicer/pull/6343))

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [May 1, 2022, 12:15pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/4 "2022-05-01T12:15:21Z")

</div>

Updates:

- Slicer v5.0.1 has been tagged and packages are being generated. See dashboard [here](https://slicer.cdash.org/index.php?project=SlicerStable&date=2022-05-01&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=)

Details:

- Issue [#6344](https://github.com/Slicer/Slicer/issues/6344) has been addressed
- Dashboard scripts have been tweaked to also backup the `site-packages` directory before building the extensions. See details [here](https://github.com/Slicer/DashboardScripts/commit/b3f057d1fbf65efb01bb2c586aada5acfcb57434).

Next steps

- The download [site](https://download.slicer.org/) displays `None` instead of the package version
- Finalize part 2 of the release checklist available at [Release Slicer v5.0 · Issue #6337 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/issues/6337)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [May 2, 2022, 3:45am UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/5 "2022-05-02T03:45:39Z")

</div>

Updates:

- Build of applications and extensions completed for both macOS and Windows 👌 ✅
- Due to a network failure related to download of some test datasets (See [here](https://slicer.cdash.org/viewBuildError.php?buildid=2677780)), the **Linux build has been re-started and is in progress** ⏳ See dashboard [here](https://slicer.cdash.org/index.php?project=SlicerStable&date=2022-05-02&filtercount=1&showfilters=1&field1=site&compare1=63&value1=metroplex).

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [May 2, 2022, 7:27pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/6 "2022-05-02T19:27:01Z")

</div>

A post was split to a new topic: [Availability of Slicer 5.0 on ArchLinux](https://discourse.slicer.org/t/availability-of-slicer-5-0-on-archlinux/23245)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [May 6, 2022, 6:56am UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/7 "2022-05-06T06:56:03Z")

</div>

Updates:

- Slicer `v5.0.2` has been tagged and packages are being generated. See dashboard [here](https://slicer.cdash.org/index.php?project=SlicerStable&date=2022-05-06&filtercount=1&showfilters=1&field1=buildname&compare1=63&value1=)
- Regular will be resumed tomorrow

Notes:

- For list of backported commits. See [Comparing v5.0.1...maintenance/5.0 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/compare/v5.0.1...maintenance/5.0)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [May 20, 2022, 7:59am UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/8 "2022-05-20T07:59:53Z")

</div>

Updates:

- Slicer `v5.0.2` packages are now available for download at [https://download.slicer.org](https://download.slicer.org) 🚀

Known issues:

- Endoscopy module issue. Fixed in [Slicer@3d66964c5](https://github.com/Slicer/Slicer/commit/3d66964c524a58b2583aac051e1310a5019d0039) and candidate for backport targeting `v5.0.3`

Next:

- Finalize announcements

---

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [May 25, 2022, 9:11am UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/9 "2022-05-25T09:11:17Z")

</div>

The module updates are not integrated in the stable release, they do upgrade normally in the nightly package. Is there any plans to backport the updates to the stable branch? When shall we expect this feature?

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [May 26, 2022, 9:00am UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/10 "2022-05-26T09:00:44Z")

</div>

When you say “module updates” what do you refer to? Extension updates? If so, you can update your extension repo hash in the s4ext in the branch of the stable version in ExtensionIndex:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/b/1/b17eba364ea05426919f6d660668c1414199f1e8.png)

---

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [May 26, 2022, 1:10pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/11 "2022-05-26T13:10:59Z")

</div>

it is there [ExtensionsIndex/OpenDose3D.s4ext at 5.0 · Slicer/ExtensionsIndex · GitHub](https://github.com/Slicer/ExtensionsIndex/blob/5.0/OpenDose3D.s4ext)

So I don’t know why the latest changes are not integrated

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [May 26, 2022, 1:51pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/12 "2022-05-26T13:51:59Z")

</div>

[https://slicer.cdash.org/index.php?project=SlicerStable&date=2022-05-25](https://slicer.cdash.org/index.php?project=SlicerStable&date=2022-05-25)

^ May 25th 2022 shows the following:

- Windows: OpenDose started building at 10:53 UTC
- Linux: OpenDose extension started building at 8:56 UTC
- macOS: OpenDose extension started building at 23:14 UTC

These all were of OpenDose hash 324ebe4 which matches the current latest at [Commits · master-stable · OpenDose / SlicerOpenDose3D · GitLab](https://gitlab.com/opendose/opendose3d/-/commits/master-stable/).

@Alex_Vergara your post yesterday was at 9:11 UTC. It appears you had posted before the extensions builds had fully completed for that day.

The runs from the previous day on May 24th ([CDash](https://slicer.cdash.org/index.php?project=SlicerStable&date=2022-05-24)) had varying git hashes of OpenDose being used because you had committed to [Commits · master-stable · OpenDose / SlicerOpenDose3D · GitLab](https://gitlab.com/opendose/opendose3d/-/commits/master-stable/) during the middle of the extension builds. The Windows build of OpenDose that day started at 12:08 UTC, but OpenDose hash 324ebe4 wasn’t committed until 13:19 UTC. While the macOS build of OpenDose did have hash 324ebe4 because it started at 21:42 UTC.

---

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [May 26, 2022, 5:15pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/13 "2022-05-26T17:15:35Z")

</div>

it is working today, thanks for the explanation

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [July 7, 2022, 10:32pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/14 "2022-07-07T22:32:37Z")

</div>

Updates:

- Slicer `v5.0.3` will be tagged shortly and packages will be generated this evening 🚀
- Regular preview and nightly builds will be **disabled** and resumed tomorrow

Notes:

- Most of the commits added to `main` have been backported commits. See [https://github.com/Slicer/Slicer/pull/6398/commits](https://github.com/Slicer/Slicer/pull/6398/commits)
- The changes related to the rename of `master` to `main` have **not** been backported
- Since only 100 commits were [allocated](https://github.com/Slicer/Slicer/blob/df1116d7685d8e9ea903aab47141224a14db62cf/CMakeLists.txt#L315-L316) for the patch releases:
  - some of the commit have been squashed together and started with `Backport ...` (for example see [82a8e54b4](https://github.com/Slicer/Slicer/pull/6398/commits/82a8e54b4eaece3952639e579f371fd6900a7199))
  - there are now 82 commits on top of `v5.0.0`

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [July 8, 2022, 6:27am UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/15 "2022-07-08T06:27:20Z")

</div>

Updates:

- Slicer `v5.0.3` has been tagged and packages are being generated. See dashboard [here](https://slicer.cdash.org/index.php?project=SlicerStable&date=2022-07-08)
- Regular will be resumed tomorrow

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [July 8, 2022, 10:45pm UTC](https://discourse.slicer.org/t/release-of-slicer-5-0-in-progress-regular-builds-are-disabled/23187/16 "2022-07-08T22:45:43Z")

</div>

Update:

- Package have been generated and will be signed on Monday
- Regular nightly build will resume this evening