Releasing a plugin
In order to release a plugin, you need to have commit access to the SONAR-PLUGINS forge. If not, ask for it on dev mailing-list.
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 and preferably have tests
- run mvn deploy in order to publish the snapshot version for tests
Prepare for the first release
When a plugin is ready to have its first release, you should do the following :
- Set the <scm> tag in the pom :
- Check that group id is org.codehaus.sonar-plugins in pom.xml, but not org.codehaus.sonar.plugins
- Set your Codehaus username/password in Maven settings.xml :
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, a vote should :
- have a minimum of three +1
- have no -1
Perform the Release
- Execute the maven-release-plugin, use default values :
- Once this is done, the jar file is available under http://repository.codehaus.org/org/codehaus/sonar-plugins/ and a tag has been created under http://svn.codehaus.org/sonar-plugins/tags
- Update the plugin page in Confluence (Don't forget to update the Changelog using the jiraissues macro).
- Announce the release on Sonar user mailing-list
- Twit it