-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Labels
Description
Follow the steps below to create a release of OnDemand Loop.
-
Prepare the issue
- Ensure the title starts with
Release. - Add at least one assignee to this issue.
- Add the label
release
- Ensure the title starts with
-
Create a release candidate
- Comment the following command on this issue:
/create_release_candidate - Eyes and rocket react appear when the command is received.
- This designates the current
maincommit as one to be deployed to the QA environment and comments the result with the commit hash.
- Comment the following command on this issue:
-
Verify and approve
- Test the deployment in QA
- FIXME: we do not currently have a QA test environment for LOOP as a product. Ideally this would be a generic vanilla OOD (or set of OOD versions) where we do manual testing (similar to the dev env). Instead we rely only on the automated testing. We do manual QA testing of the our local deployment after the deployment release candidate is created in our deployment repo.
- When ready to proceed, add a comment (which the next command will look for) containing:
release approved
- Test the deployment in QA
-
Create the release
- Trigger the release workflow by commenting:
Replace
/create_release type=<patch|minor|major><patch|minor|major>with the desired semantic version bump. - This will use the previously saved commit hash to create a tag and a release with the new version number.
- While we are in beta, we are doing only minor releases.
- Trigger the release workflow by commenting:
-
Finish up
- Once the release workflow succeeds it will comment the version number and release notes link.
- Close this issue when everything looks good.
Only authorized users (in .github/workflows/slash_command_listener.yml) can execute the slash commands above.