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
...
1) git checkout b19.2 (switch into "long-live" release branch);
-- TODO: create rerlease branch
— TODO: pickup needed commits from mail development stream (master) into relaese branch
...
4) mvn versions:set -DnewVersion=19.2.3-SNAPSHOT (here we set the version of bugfix release, it conists of preparing relese's number with added prefix: "-SNAPSHOT");-- add commit ????
TODO: add commit of version changes in pom.xml
5) mvn --batch-mode -DautoVersionSubmodules=true release:clean release:prepare (runs maven release buld process. Here release number and rest of data set up automatically without any dialogs, based on version's set from previous step);
6) git push && git push --tags (pushing local changes, release notes in this case, with tags to remote stash. These changes are pushed to remote long-live branch b19.2)
TODO: create pull request of pushed remote release branch to long-live branch b19.2.
TODO: After merging, rest of release related finishing steps nededs to be completted, see below.
7) Run release job (log in to Jenkins and trigger Build Now). Please don't forget to build release's envitronment !!!
...
`mod-inventory-storage 19.2.3` has been released https://github.com/folio-org/mod-inventory-storage/releases/tag/v19.2.3