...
Currently, we have 8 UI modules within ERM:
stripes-erm-components
ui-agreements
ui-licenses
ui-erm-comparisons
ui-local-kb-admin
ui-plugin-find-agreement
ui-plugin-find-license
ui-plugin-find-eresource
We follow the FOLIO version-numbering scheme to version our apps/plugins. This is the same as the official semver documentation.
...
By this time, it is considered that all your UI modules are synchronized with the relased stripes version and th, and you have also updated your UI modules to their respective major/minor version.
...
3) Manually browse through individual modules with the browser console open and ensure there are no glaring warnings/errors in the console.
4) Go through all the dependencies in the package.json and see verify if all of them the ones that require updation are updated (Note: Each of the erm UI modules depends on stripes-erm-components, so its important that each of those modules is dependent on the version of stripes-erm-components that is going to be released)
...
1. git checkout -b 'v3.0'
2. git add package.json CHANGELOG.md
3. git commit -m 'Release 3.0.0'
4. git tag v3.0.0
5. git push --set-upstream origin v3.0
6. git push --tags
7. Navigate to https://jenkins-aws.indexdata.com/job/folio-org/job/ui-agreements/view/tags/ (assuming you are releasing the ui-agreements module)
8. Login to jenkins and check for the 3.0.0 tag from the list (from the dropdown beside the tag, click the build now button)
9. Once the build has started you can click the full stage view option to see the build
10. Once the build is all done and green, you can navigate to https://repository.folio.org/#browse/browse:npm-folio and see if your module has been published.
11. Navigate to https://github.com/folio-org/ui-agreements/tags and you should see the tag there. Click on it and draft a new release.
12. Paste the CHANGELOG for that module in the Describe this release section and click publish release
13. Send the release announcement to the #releases slack channel once done.
After the release:
1) Merge the branches pushed to github for the respectve modules into their masters
2) Bump the minor versions of all the UI modules with a new CHANGELOG version entry so that any new code being added
...
doesn't accidentally go towards the just released version.
Note: Do not delete the branch you have just merged into the master as you can base off of these branches in case there is a requirement for a hotfix release.
For further information on the patch/hotfix release procedure refer to this section https://github.com/folio-org/stripes/blob/master/doc/release-procedure.md#patch-release-procedures from the official stripes release documentation.
...