We decided to cut releases in order to keep track of what is being ran inside of CI/QA/PROD.
Is your feature request related to a problem?
We need a way to correlate the code that is being ran in production with the stable branch.
Describe the solution you'd like
1. Merge the master changes into stable - giving release notes in the PR
2. Create a release off of the stable branch - copy release notes from PR
3. Submit a PR to the E2E repo to change the version - for both CI/QA/PROD (CI/QA should be PROD release + 0.0.1)
4. Manually deploy to PROD (from jenkins)
Acceptance Criteria:
[x] Verify that we have released 0.2.0 in production and that we have a matching release/ documentation for releasing
Feature description:
We decided to cut releases in order to keep track of what is being ran inside of CI/QA/PROD.
Is your feature request related to a problem?
We need a way to correlate the code that is being ran in production with the stable branch.
Describe the solution you'd like
Acceptance Criteria: