The Oncall is responsible for releasing a new version of CiviForm on Tuesday during their rotation and general upkeep through their rotation. This is an aid for each rotation, but the docs are the source of truth.

Rotations begin each Monday, with the release happening on Tuesday.

Please check off all items at their appropriate times during your rotation.

Resources:

• Oncall Guide
• Release Guide

Task list:

Release

• Choose a new version number in the format vX.Y.Z. If this is an unscheduled release in order to fix a bug, increment Z. Otherwise, increment Y and set Z to 0. Do not increment X without a discussion with the rest of the engineering team.
• Create a Draft Release by 12 PT on Tuesday
  • Ensure both the civiform and cloud-deploy-infra repos are tagged appropriately after running the Create Release action.
• Contact Matthew Sprenke for QA on Slack
• If Matthew is unavailable have the general team attempt a best-effort QA.
• After QA, publish the release
• If the release is going to be published later than Wednesday EOD, email civiform-announce@googlegroups.com and civiform-technical@googlegroups.com to let admins know when to expect the next release.
• After publishing, email release notes
  • The email should include both a link to the release notes on GitHub, and a sentence or two summarizing what is in the release. It should be friendly to non-technical readers (think CiviForm and Program Admins). Feel free to use phrases like "small usability improvements" rather than listing each improvement. Edit the GitHub release notes and add this small summary to the top of it as well.
• Upgrade the demo site config files to the latest version by running this action then approving and merging the generated PR.

General

• Create an Oncall issue for the next rotation, and assign to the next oncall
• Check Security lists daily
• Check #eng-ci Slack channel daily to monitor failed pushes and e2e test runs
• Check needs triage bugs daily to ensure there aren't any P0s
• Check for dependency updates
  • Do your best to resolve any problematic dependency updates that break tests during your shift. If you start work on a dependency but are unable to fully resolve it during your oncall shift, hand it off to the next person.
  • For any broken updates that require very, very large changes, please create a new GitHub issue and add the "needs-triage" label so that Exygy can prioritize fixing these issues. Also, mark the Renovate PR as "draft" and add a comment on the PR with the link to the new issue.
  • Renovate PRs for civiform/civiform
  • Renovate PRs for civiform/civiform-staging-deploy
  • Renovate PRs for civiform/cloud-deploy-infra