# Science Pipeline release 19.0.0 - Status and discussion **URL:** \ **Category:** DM Notifications\ **Tags:** stack-releases\ **Created:** [October 22, 2019, 12:43am UTC](https://www.rubin.community/t/science-pipeline-release-19-0-0-status-and-discussion/3900 "2019-10-22T00:43:06Z")\ **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:** [October 22, 2019, 12:43am UTC](https://www.rubin.community/t/science-pipeline-release-19-0-0-status-and-discussion/3900/1 "2019-10-22T00:43:06Z")
Here is where we currently are in the release process. Current step in bold. Summary * * * Establishing if Science Pipeline is ready for next release. Tentative target date to close the release on November 27th, 2019. Release Jira issue: [https://jira.lsstcorp.org/browse/DM-18119](https://jira.lsstcorp.org/browse/DM-18119) Release Precursor Steps * * * 1. Identify any pre-release blockers (“must-have features”) To all science pipeline contributors, please check if there are outstanding issues that have to be included in the next 19.0.0 release. If no outstanding issues are highlighted, and no problems are found, we plan to use the next weekly build (w\_2019\_43 from October the 26th) as the starting point for the 19.0.0 major release. 2. Wait for contributors to clear 3. The weekly build identified as the starting point for the release is **w\_2019\_46**. Release Engineering Steps * * * 1. Git Tag v19.0.0.rc1 2. Eups publish rc1 candidate (based on b4576) (also w\_2019\_46) 3. Branch v19.0 of newinstall.sh 4. Github release lsst\_demo v19 5. Wait for the first round of bugs to clear 6. Repeat last 2 steps, -rc2 and rc3 candidates <-- final candidate is rc1 7. Confirm DM Externals are at stable tags 8. Full OS testing (see [https://ls.st/faq](https://ls.st/faq) ) 9. Tag DM Auxilliary (non-lsst\_distrib) repos 10. **Git Tag 19.0.0, rebuild, eups publish** Binary release steps * * * 1. Produce factory binaries (produced using tarball-matrix) 2. Test factory binaries 3. **Gather contributed binaries** Documentation Steps * * * [Integration on v19.0 branch of pipelines\_lsst\_io](https://github.com/lsst/pipelines_lsst_io/pull/TBD) 1. Update Prereqs/Install 2. Gather Release notes 3. Gather Metrics report 4. Update Known Issues 5. **Email announcement** ---
**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:** [October 23, 2019, 4:27pm UTC](https://www.rubin.community/t/science-pipeline-release-19-0-0-status-and-discussion/3900/2 "2019-10-23T16:27:01Z")
The DM-CCB discussed the pending issues this morning: - DM-21169 - DM-20574 - DM-20937 - DM-18036 - DM-19207 and agreed that the start of the release process can wait a couple of weeks, until these issues are resolved. There should be minimum impact to the release availability date (or no impact at all). ---
**Author:** ![jbosch](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jbosch/32/12_2.png) [@jbosch](https://www.rubin.community/u/jbosch)\ **Post date:** [November 12, 2019, 4:03pm UTC](https://www.rubin.community/t/science-pipeline-release-19-0-0-status-and-discussion/3900/3 "2019-11-12T16:03:37Z")
Does the update to the schedule mean that some later weekly will be used as the basis, or that the changes from the blocking issues will be back-ported to a branch off of `w_2019_43`? I’m interested primarily because I’m not sure when deprecated interfaces merged to master ~now should be marked as removable (in particular, [RFC-644](https://jira.lsstcorp.org/browse/RFC-644)). ---
**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:** [November 12, 2019, 4:59pm UTC](https://www.rubin.community/t/science-pipeline-release-19-0-0-status-and-discussion/3900/4 "2019-11-12T16:59:27Z")
There are still 4 issues open, blocking the release: - DM-17924 to be removed from the blockers to 19.0.0 - DM-22191 nothing done so far on this issue, looking on its status - DM-20571 should be merged today - DM-21169 should be also approved and merged today If: - we manage to clear all blockers by tomorrow the 12th by the end of the day - no other problems nor blocker issues are found we will start the release process with the next weekly w\_2019\_46. ---
**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:** [December 6, 2019, 8:27pm UTC](https://www.rubin.community/t/science-pipeline-release-19-0-0-status-and-discussion/3900/5 "2019-12-06T20:27:13Z")
The Science Pipelines 19.0.0 release is now available: > [@LSST Science Pipeline release version 19.0.0 now available](http://www.rubin.community/t/lsst-science-pipeline-release-version-19-0-0-now-available/3951): > > Version 19.0.0 of the LSST Science Pipeline is now available. Extensive documentation including installation instructions, release notes, and scientific characterization are available at: [https://pipelines.lsst.io](https://pipelines.lsst.io). This release offers native binary packages for recent releases 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-v19-0-0](https://pipelines.lsst.io/releases/notes.html#release-v19-0-0) Many thanks to @K…