Skip to content

Latest commit

 

History

History
35 lines (22 loc) · 1.46 KB

RELEASE_PROCEDURE.md

File metadata and controls

35 lines (22 loc) · 1.46 KB
Raw

Release procedure

When you release fixed version of SonarQube SpotBugs Plugin, please follow these procedures.

  • create topic branch from master branch
git checkout -b master-release

  • Make sure profile XMLs are updated. See generate_progiles/README.md for detail.

  • change version number in pom.xml to stable version (e.g. 1.2.3), then commit changes

mvn versions:set -DnewVersion=1.2.3
  • change version number in pom.xml to next development SNAPSHOT version (e.g. 1.2.4-SNAPSHOT), then commit changes
mvn versions:set -DnewVersion=1.2.4-SNAPSHOT
  • push your topic branch and propose a pull request
  • after merging your pull request, create a GitHub Release with the commit which has stable version in pom.xml. The name of tag should have no prefix nor suffix, e.g. 4.0.0

Release to Maven Central

When we push tag, the build result on Travis CI will be deployed to Sonatype Nexus. Check Sonatype official page for detail.

Release to SonarQube Marketplace

sonar-update-center-action will handle necessary procedures. Please confirm that the PR is made in SonarSource/sonar-update-center-properties, and a topic is posted to the community forum.