Update: We are currently addressing outstanding issues and cleaning up the issue tracker, once completed (in the two weeks timeframe), we will cut the 4.8 release.
If there are any outstanding issues you would like to see addressed for the release, report them on https://issues.slicer.org/ and reply to this topic. We would also be happy to review patches.
Extensions: We will also do a final call (by email) to extension maintainers so that we integrate PRs or fix their extensions. Without any response, we will either remove the extension from extension index or transfer the GitHub project into the Slicer organization so that it can be maintained by the community. See Slicer extensions: Action required by maintainers
Next steps Following the 4.8 release, we will transition to Qt5 and VTK8 and start working on Slicer 5.0. Transition to python 3 is also planned.
Here is a google document where I started to aggregate the ChangeLog for the announcements. I basically went through the ~1000 commit since Slicer 4.6 and grouped them into categories by omitting and/or rephrasing some.
As indicated above, there was an error in the dashboard script. While creating the release scripts, I used the wrong one as a template and it was missing:
# This will ensure compiler paths specified using the cache variable are used
# consistently.
set(ENV{CC} "/dev/null")
set(ENV{CXX} "/dev/null")
[...]
set(ADDITIONAL_CMAKECACHE_OPTION "
CMAKE_C_COMPILER:FILEPATH=/usr/bin/gcc-4.6
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/g++-4.6
[...]
")
which led the linux build to use the older compiler g++ 4.4 (available in the PATH) on that platform.
Instead , the script should explicitly use g++ 4.6
