Science Pipeline release 17.0 - Status and discussion

stack-releases
Tags: #<Tag:0x00007f7f728543e8>

(Gcomoretto) #1

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 November 25ft 2018.

Release Precursor Steps


  1. Identify any pre-release blockers (“must-have features”) :tools:

To all science pipeline contributors, please check if there are outstanding issues that have to be included in next 17.0 release. If no outstanding issues are highlighted, and no problems are found, we plan to use next weekly build (w_2018_42 from October the 22nd) as starting point for the 17.0 major release.

  1. Wait for contributors to clear

Release Engineering Steps


  1. Git Tag v17.0.rc1

  2. Eups publish rc1 candidate (based on bXXXX) (also w_2018_42)

  3. Branch v17 of newinstall.sh

  4. Github release lsst_demo v17

  5. Wait for first round of bugs to clear

  6. Repeat last 2 steps, -rc2 and rc3 candidates <-- final candidate is rcX

  7. Confirm DM Externals are at stable tags

  8. Full OS testing (see https://ls.st/faq )

  9. Tag DM Auxilliary (non-lsst_distrib) repos

  10. Git Tag 17.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 v17.0 branch of pipelines_lsst_io


(John Swinbank) #2

To all science pipeline contributors, please check if there are outstanding issues that have to be included in next 17.0 release. If no outstanding issues are highlighted, and no problems are found, we plan to use next weekly build (w_2018_42 from October the 22nd) as starting point for the 17.0 major release.

Since this release is addressing the milestone LDM-503-09a, the “must-have features” are listed in LDM-564 §3.12. Not all of those features will be in w_2018_42. We (you, @yusra, @fritzm, I) should probably take it to e-mail to establish exactly when those features will be landing and/or which we can cut from the release (DM-DAX-8, I’m looking at you…!).


(John Swinbank) #3

Tracking ticket for this release, capturing relevant blockers, is DM-16397.


(Gcomoretto) #4

So far there are still following issues open that blocks the start of the release process:

DM-11783, that imply the resolution of:

DM-16128
DM-16374


(John Parejko) #5

Are you sure you meant DM-15221? That’s not a release blocker that I can see. I’m guessing you meant DM-15751?


(Gcomoretto) #6

Right, DM-15221 seems not to be blocker for the epic FM-11783, so it is probably not blocking the release either.

I am not sure if DM-15751 shall be considered blocker for the release. @swinbank?


(John Swinbank) #7

I agree that DM-15221 is not blocking the release. DM-15751 is, but only indirectly (it blocks the completion of DM-11783, which in turn blocks the release).

It’s likely that we’ll change the blockers over the next few days (in particular, I don’t think it’s necessary for DM-15846, which is also part of DM-11783, to block the release). Given that, I suggest it’s easiest just to refer to the list on DM-16397 for a guaranteed-correct (…modulo typos) set of blockers.


(Gcomoretto) #8

Thank you John for the clarification. I would suggest to avoid epics as blocker to the release issue, and just list the relevant blocking story issues.