Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

Prepare to release

  • Make sure the wiki page is up to date
  • All JIRA issues included in the release should be closed
  • Plugin must be documented
  • Check the source code quality of the plugin : The SQALE index must be A and between two releases the SQALE remediation factor must not increase
  • Run mvn deploy in order to publish the snapshot version for tests

Prepare your first release

When a plugin is ready to have its first release, you should do the following :

  1. Set the <scm> tag in the pom :
  2. Check that group id is org.codehaus.sonar-plugins in pom.xml, but not org.codehaus.sonar.plugins
  3. Set your Codehaus username/password in Maven settings.xml :
  4. Install Codehaus SSL certificates into JDK
  5. Request on the development mailing list that a Bamboo build is added for the plugin

Call a Vote

Before a release can occur, a vote typically takes place. This is initiated with an email to the dev mailing list with a link to the snapshot version, preferably with a subject that starts with [VOTE]. Explain the plugin, status and any other info you feel relevant. The standard is to wait 72 hours for responses. This gives other developers time to verify the validity of the plugin before placing their vote. Votes are represented as numbers between -1 and +1, with -1 meaning 'no' and +1 meaning 'yes.'

Only Sonar plugin commiters can vote. To pass, lazy consensus is used, so a vote should have no -1.

Perform the Release

  1. Close the vote on the dev mailing list
  2. Execute the maven-release-plugin, use default values :
  3. Update the plugin page with new version info (the jar file is available under
  4. Update the Changelog using the jiraissues macro
  5. Release the version in JIRA
  6. Update the version compatibility matrix
  7. Announce the release in the mailing-lists, and (you must subscribe to these lists in xircles )
  8. Send an email to to ask for adding the release to Update Center. This redundant step will be improved later.
  9. Tweet (big grin)
  • No labels