I want to have a Mojaloop release v16.1.0 (version to be confirmed as part of the story) that is successfully validated by the Golden path tests
so that I can adopt and use a version of Mojaloop Switch services bundle that is tested and contains the latest features enhancements and bug fixes added in PI-23, 24 (includes Merchant payments, performance enhancements done post ML v16.0.0 - Congo and several security patches)
Acceptance Criteria:
[ ] Update "APP VERSION" for each chart.yaml
[ ] Helm RC Release is validated on Moja2 to achieve 100% result with TTK GoldenPath
[ ] Helm RC Release is validated with PISP provisioning and test collection (TTK) with 100%
[ ] Helm RC Release is validated with Bulk test collection (TTK) with 100%
[ ] QA (Golden path) on deployments done on AWS Moja2 environment is done
[ ] Bugs are logged based on observations, failures
[ ] Bugs logged are fixed if critical to make subsequent releases in individual services (or Helm)
[ ] All the changes needed for supporting the Helm Release are done
[ ] Helm chart is published
[ ] Release notes are published
[ ] Test cases are published (TTK)
[ ] TTK tests run successfully as Post-Hook jobs and Tests
Notes:
Complexity: Medium - Involves all core and supporting services
Uncertainty: Medium
Tasks:
[ ] Ensure all core services and services included in release follow standards for
[ ] Dependabot alerts
[ ] Snyk alerts
[ ] codeowners files
[ ] Branch protection rules on main branches verified
[ ] Review open issues
[ ] Review open pull requests
[ ] Review audit exceptions provided and minimize the list
[ ] Update manifests for "release PR" GH actions WF
[ ] Validate the PR released and the process
[ ] Deploy, validate RC on AWS Moja2
[ ] Validate merchant test collection works as expected
[ ] Identify issues with QA Scripts if any - fix them and retest
[ ] QA for bugs, regressions, log them
[ ] Fix bugs logged if critical
[ ] Validate with TTK GP collection
[ ] TTK test-cases repo Release is published
[ ] Release notes for helm RC is drafted
[ ] Guidance for migration from Release (may have to be a separate story if sufficiently big / complex)
[ ] Update release notes with Upgrade Strategy Guide link
[ ] Helm Release is published
[ ] Deployment of released Helm on Moja2
[ ] Helm release is deployed on Moja2 successfully
[ ] Regression testing on Moja2 using TTK collections
[ ] GP collection
[ ] Core Bulk collection
[ ] Third-party collection
[ ] SDK Bulk collection
[ ] SDK R2P collection
[ ] Merchant payment test collection
[ ] Validation using CGS Golden path regression tests etc on Moja2
[ ] Test upgradability from previous release
[ ] Deployment of released Helm on Moja1
[ ] Helm release is deployed on Moja1 successfully
[ ] Validation using Golden path regression tests etc on Moja1
[ ] GP collection
[ ] Core Bulk collection
[ ] Third-party collection
[ ] SDK Bulk collection
[ ] Merchant payment test collection
[ ] Validation using CGS Golden path regression tests etc on Moja1
[ ] Validate daily cronJobs on Moja1 for GP and Cleanup scripts
Goal:
As aML OSS adopterI want tohave a Mojaloop release v16.1.0 (version to be confirmed as part of the story) that is successfully validated by the Golden path testsso thatI can adopt and use a version of Mojaloop Switch services bundle that is tested and contains the latest features enhancements and bug fixes added in PI-23, 24 (includes Merchant payments, performance enhancements done post ML v16.0.0 - Congo and several security patches)Acceptance Criteria:
Notes:
Complexity: Medium - Involves all core and supporting services Uncertainty: Medium
Tasks:
Done
Pull Requests:
Issues:
Follow-up:
Dependencies:
Accountability: