# Update: Slicer 4.10 release will be initiated tomorrow morning

**URL:** <https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422>\
**Category:** Development\
**Tags:** release-process\
**Created:** [October 17, 2018, 1:57am UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422 "2018-10-17T01:57:45Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![rkikinis](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rkikinis/32/791_2.png) [@rkikinis](https://discourse.slicer.org/u/rkikinis)\
**Post date:** [November 1, 2018, 9:20pm UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422/21 "2018-11-01T21:20:53Z")

</div>

I downloaded slicer and installed it. Everything works like a charm on the MAC. No error messages, just the notification that the software was downloaded from [kitware.com](http://kitware.com)

I am very happy. Thanks to all who contributed to this.

Best

Ron

---

<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:** [November 1, 2018, 9:37pm UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422/22 "2018-11-01T21:37:31Z")

</div>

> [@rkikinis](#):
>
> we should update the [slicer.org](http://slicer.org) top page.

This is indeed the last step of the release process. See [Publish\_Slicer\_Announcement](https://www.slicer.org/wiki/Documentation/Nightly/Developers/ReleaseProcess#Publish_Slicer_Announcement)

Unless you think differently, I suggest we finalize the update as soon as we are ready to publish the document “Slicer 4.10: Summary, Highlights and Changelog”. See [Slicer 4.10: Summary, Highlights and Changelog](https://discourse.slicer.org/t/slicer-4-10-summary-highlights-and-changelog/4610)

---

<div class="post-metadata">

**Author:** ![rkikinis](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/rkikinis/32/791_2.png) [@rkikinis](https://discourse.slicer.org/u/rkikinis)\
**Post date:** [November 1, 2018, 9:55pm UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422/23 "2018-11-01T21:55:30Z")

</div>

Hi JC

Thanks for the clarifications.  
Sounds good.

Best

Ron

---

<div class="post-metadata">

**Author:** ![Fernando](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fernando/32/5640_2.png) [@Fernando](https://discourse.slicer.org/u/Fernando)\
**Post date:** [November 4, 2018, 5:34pm UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422/24 "2018-11-04T17:34:26Z")

</div>

I have updated the `brew` cask:

> <https://github.com/Homebrew/homebrew-cask/pull/54491>
>
> After making all changes to the cask:
> 
> \- \[x\] \`brew cask audit --download {{cask\_…file}}\` is error-free.
> \- \[x\] \`brew cask style --fix {{cask\_file}}\` left no offenses.
> \- \[x\] The commit message includes the cask’s name and version.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [November 5, 2018, 6:49pm UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422/25 "2018-11-05T18:49:58Z")

</div>

@jcfr just realized that nightly packages are not still signed. I guess this was expected, but took me a bit by surprise.

---

<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:** [November 5, 2018, 7:02pm UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422/26 "2018-11-05T19:02:39Z")

</div>

> nightly packages are not still signed

That is correct. Signing is a semi-automatic process requiring user interaction.

The good news is that we are now all the piece to move forward with setting up our automated signing infrastructure.

---

<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:** [January 10, 2019, 4:59pm UTC](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422/29 "2019-01-10T16:59:03Z")

</div>

Following this week hangout [2019.1.7 Hangout](https://discourse.slicer.org/t/2019-1-7-hangout/5305/3?u=jcfr), Slicer 4.10.1 will be released next week.

[Previous page](https://discourse.slicer.org/t/update-slicer-4-10-release-will-be-initiated-tomorrow-morning/4422.md?page=1)