# LSST stack release version 15.0 now available **URL:** \ **Category:** DM Notifications\ **Tags:** stack-releases\ **Created:** [April 10, 2018, 9:48pm UTC](https://www.rubin.community/t/lsst-stack-release-version-15-0-now-available/2827 "2018-04-10T21:48:01Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![gcomoretto](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/gcomoretto/32/640_2.png) [@gcomoretto](https://www.rubin.community/u/gcomoretto)\ **Post date:** [April 10, 2018, 9:48pm UTC](https://www.rubin.community/t/lsst-stack-release-version-15-0-now-available/2827/1 "2018-04-10T21:48:01Z")
Version 15.0 of the LSST software stack that includes the LSST Science Pipelines is now available. Extensive documentation including installation instructions, release notes and scientific characterization are available as usual at: [https://pipelines.lsst.io](https://pipelines.lsst.io) This release offers native binary packages for recent flavours of RHEL and MacOS which will speed up installation times for many users. Major changes in functionality and/or interfaces are listed here: [https://pipelines.lsst.io/releases/notes.html#release-v15-0](https://pipelines.lsst.io/releases/notes.html#release-v15-0) Many thanks to @frossie for guiding me through the release process, to @KSK for preparing the characterization report and drafting the release note, to @timj and @swinbank for all the support provided, and @jsick for the major update to [pipelines.lsst.io](http://pipelines.lsst.io). And of course many thanks to all DM developers who contributed to this release. ---
**Author:** ![timj](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/timj/32/10_2.png) [@timj](https://www.rubin.community/u/timj)\ **Post date:** [April 10, 2018, 10:56pm UTC](https://www.rubin.community/t/lsst-stack-release-version-15-0-now-available/2827/2 "2018-04-10T22:56:34Z")
@KSK reminds me that we didn’t mention the `libiconv` issue in the Known Problems section of the release notes. `log` can fail to build if the conda libiconv package is installed. It needs to be uninstalled when `apr_util` is building. See [DM-12105](https://jira.lsstcorp.org/browse/DM-12105). ---
**Author:** ![heather999](https://avatars.discourse-cdn.com/v4/letter/h/f4b2a3/32.png) [@heather999](https://www.rubin.community/u/heather999)\ **Post date:** [April 11, 2018, 12:36am UTC](https://www.rubin.community/t/lsst-stack-release-version-15-0-now-available/2827/3 "2018-04-11T00:36:34Z")
@timj Does that mean if one were doing an eups disturb install from source, one could start with apr\_util and then go back, reintroduce libiconv in their conda env, and proceed to build the rest of lsst\_distrib? I ask since the builds take awhile at NERSC and we use an external conda installation which is shared with other stack builds and anaconda python users. It’d be nice to reduce the amount of time where libiconv is removed. ---
**Author:** ![timj](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/timj/32/10_2.png) [@timj](https://www.rubin.community/u/timj)\ **Post date:** [April 11, 2018, 3:55am UTC](https://www.rubin.community/t/lsst-stack-release-version-15-0-now-available/2827/4 "2018-04-11T03:55:08Z")
> [@heather999](#): > > one could start with apr\_util and then go back, reintroduce libiconv in their conda env, and proceed to build the rest of lsst\_distrib? Yes. I believe so. ---
**Author:** ![FabioHernandez](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/fabiohernandez/32/82_2.png) [@FabioHernandez](https://www.rubin.community/u/FabioHernandez)\ **Post date:** [April 11, 2018, 8:53am UTC](https://www.rubin.community/t/lsst-stack-release-version-15-0-now-available/2827/5 "2018-04-11T08:53:41Z")
`v15.0` is also available in the cloud via the CernVM-FS binary distribution, for both Linux and macOS. Details [here](https://github.com/airnandez/lsst-cvmfs).