Release Checklist
Dileep Gadiraju edited this page Mar 30, 2023
·
1 revision
- In profile menu of the App, About menu should always show the current release version of the App .
- When we prepare release notes always attached unsigned apk with it and that apk BASE_URL should be 'TO_BE_REPLACED' .
- apkVersion in config.js should also point to latest release .
- Always attach all the layouts in the release .
- Swagger documentation and postman collection should always be updated .
- When we add any new layout always add generated rois in data/layout folder .
- Whenever new release is cut test Backwards Compatibility with old version backend APIs. Any new update will not break previous releases .
- Always create release tag from main branch . List down all the new features ,enhancement and bug fixes in that release note provide link as well .
- Always test your apk with up url as well .
- Documentation to be verified and published @ https://saral.sunbird.org/.
- attach aab file with the release .
- attach test case report of jest unit test case .