1 of 5

ServiceX

Release process and RC3

​

​

1

​

ServiceX Working Meeting�10/2/20

Andrew Eckart

Enrico Fermi Institute

University of Chicago

2 of 5

Proposed Release Checklist

  • Create release branch off main branch (“develop” for app and chart)
  • Freeze dependencies in requirements.yaml and setup.py
  • Verify Read the Docs build for release branch
  • Update links to docs (in README, website, and welcome emails)
  • Confirm DockerHub has a tag for this release at sslhep/servicex_app
  • Fix image versions in default values.yaml
  • Publish new version of servicex chart to ssl-hep/servicex helm repo
  • Make deployments to RIVER.
  • Make sure docs link to correct deployments.
  • Send announcement to mailing list

2

3 of 5

Release Cycle

  • Pre-release
    • Use milestones to track issues that should be resolved and PRs that should be merged in the next release
  • During release
    • Create an issue for the release (e.g. “Release 1.0.0-RC3 checklist”)
    • Complete checklist items
  • Post-release
    • Move any unresolved issues/PRs to the next milestone

3

4 of 5

Remaining items for RC3

  • ServiceX#197 / ServiceX_App#67 - configure links to docs
  • Fix 500 internal server error on query transformation request 404
    • Fixed in ServiceX_App#56, but we might want something more targeted
  • Clean up deployment docs
  • ServiceX_frontend#197 - new auth system
  • ServiceX_frontend#119 - ignore local cache (?)
  • Marketing - logo? Content for homepage?
  • Match ssl-hep/servicex chart versions to app versions?
  • Anything else?
  • Kicked to RC4: monitoring

4

5 of 5

5