Skip to content

Latest commit

 

History

History
41 lines (23 loc) · 1.75 KB

RELEASE_PROCEDURE.md

File metadata and controls

41 lines (23 loc) · 1.75 KB
Raw

Release procedure

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

Update version info

  • version in build.gradle
  • version number in CHANGELOG.md
  • version, full_version, maven_plugin_version and gradle_plugin_version in docs/conf.py

Release to Maven Central

When we push a tag, the build result on GitHub Actions will be deployed to the SonaType Nexus, and published to the Maven Central automatically by Gradle Nexus Publish Plugin. Then we can find artifacts in the Maven Central after several hours.

Release to Eclipse Update Site

It's automated by Github CI.

When we push tag, the build result will be deployed to eclipse-candidate repository. When we push tag and its name doesn't contain _RC, the build result will be deployed to eclipse repository.

See deploy phase in .github/workflows/release.yml for detail.

Release to Eclipse Marketplace

Update version in Eclipse Marketplace page. If you have no permission, please contact with @KengoTODA or @iloveeclipse.

Release to Gradle Plugin Portal

No action necessary. When we push tag, the build result on Github CI will be deployed to Gradle Plugin Portal.

See deploy phase in .github/workflows/release.yml for detail.

Update installation manual

docs/installing.rst includes link to released binaries, update them. It is also necessary to change filename in command line example.

Release to ReadTheDocs

See docs/README.md for detail.