Do not start hotfix forcefully from master branch

[jkroepke]

In some conditions I have to backport hotfixes to older versions.

So I have to create a branch from an older tag (git checkout -b release-4.1.9 v4.1.9) apply the fixes (e.g. cherry pick from master), push the version (e.g. with

release-scripts/.hooks-default.sh

Line 71 in 285c9a5

function set_modules_version {

) create a new git tag without merging the commit pack to master.

Following steps have to been executed manually:

git checkout -b release-4.1.9 v4.1.9
mvn versions:set -DnewVersion=4.1.9.1
# do stuff manually like git cherry-pick
git tag v4.1.9.1
git push --tags

[borisskert]

Hi Joe!

for backports you can adjust your hooks in the corresponding branch to perform the release on other branches than the default develop or master.

There is a merge request (#14) which is about to being merged and which fixes the release branches not to have the snapshot version included.
Maybe in this situation we can adjust the hooks and push the release branch automatically to resolve your issue.

[DG0lden]

Hi Joe and Boris,

I've made MR (#17) that may fix this issue as well.

regards, Denys