We are using Sonarqube Developer Edition Version 7.7, and have a question on branch strategy.
We are following git-flow approach in our projects, so we have a develop and a master branch. When we’re about to release, a release branch is cut from the develop branch. Any fixes on the release branch is done through pull requests from short-lived branches to the release branch. After the release is published to public, the release branch is merged to the develop and the master branches.
In setting up SonarQube for our projects, we were wondering if release branches should be set as long-lived branches or short-lived? By default any branches start with “release” is set to be long-lived but according to the SonarQube document on branches https://docs.sonarqube.org/pages/viewpage.action?pageId=11640256 it seems like release branches meet the definition of short-lived branches.