The purpose of this page is describing module release practical procedures. Mainly these steps are based on general "Release Procedure" but contains some of refinements found in the process of recent release procedures.
...
13) Annonce in Slack about a new release in the #release thread (example of message):
`edge-oai-pmh 2.2.1` has been released https://github.com/folio-org/edge-oai-pmh/releases/tag/v2.2.1
...
2) Create a reease branch from there, for example: MODINVSTOR-524/release-19.2.3 (<release_ticket>/<release_branch_name>.
3) Cherry pick into prevoiusly created release branch all needed commits from mainstream developemnt development branch, i.e. master. Made any Make any extra fixes, if any changes needed changes , and commit them into previously created release branch*.
git cherry-pick <commit_hash>
* Don't forget to back porting extra fixes into mainstream developmet development branch, i.e. master, if these changes valuable not only for particular bugfix release.
...
7) Go to the module's repository on GitHub and create a new "Pull request" of pushed relaese branch (MODINVSTOR-524/release-19.2.3) into the "long-live release branch - b19.2 in or case,
...
and add next versions.
11) Made Make release in Jira if you have required permission for that, add next versions.
...
`mod-inventory-storage 19.2.3` has been released https://github.com/folio-org/mod-inventory-storage/releases/tag/v19.2.3