Science Pipeline release 20.0.0 - Status and discussion

Tags: #<Tag:0x00007fb380e32cf0>

Here is where we currently are in the release process. Current step in bold.

Release Precursor Steps

  1. Identify any pre-release blockers (“must-have features”)
    Contributors check if there are outstanding issues that have to be included in the next release and relate them as blocker to the issue DM-20564.
  2. Wait until all blocking issues are resolved.
  3. Create Jira issues for each release activity.
  4. Check that the weekly build is scientifically suitable to be used as the starting point for the release (w_2020_22)

Release Jira issue: https://jira.lsstcorp.org/browse/DM-20564
Weekly used as the starting point for the release is w_2020_22

The tentative target date to close the release is 2020-06-21 (instead of May 29th).

Release Engineering Steps

  1. Create first release candidate v20.0.0.rc1
  2. Release candidate v20.0.0.rc1 available:
  • Build: b4918
  • Weekly: w_2020_22
  1. Build the release candidate on supported platforms. Report bugs in Jira if any.
  2. Invite developers, contributors and downstream users to verify the release candidate and report bugs in Jira if any.
  3. Wait for bugs and additional issues to be identified, fixed and ported to the release branch.
  4. Create new release candidates if bugs / new issues have been fixed in the release branch
  5. Create official release 20.0.0 :tools:

Documentation Steps

In parallel with the engineering steps, after rc1 is available.
Integration on 20.0.x branch of pipelines_lsst_io

  1. Update Prereqs/Install
  2. Gather Release notes :tools:
  3. Gather Metrics report
  4. Update Known Issues
  5. Release availability community post :tools:

v20.0.0.rc1 now available

I have used the v20.0.0.rc1 release candidate in a few test on different platforms, without problems.
Everybody is invited to try it out (this was implicit, announcing that the rc1 is available, but better to state it explicitly).

The Science Pipelines release 20.0.0 is now available. See CLO: