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 15 Next »

  • let folks know a release is about to occur. Maybe on #groovy let people know or mail the mail list.
  • get a nice clean CVS checkout
  • make sure you've got Maven 1.0.2 or later installed
  • update the version in project.xml to the next version number & check it in
  • you need to go into the modules/xmlrpc/project.xml and update the version of groovy to the one we're about to release
  • add the release version to the project.xml's versions
  • label it as something like GROOVY_9_9_beta_9

Then in groovy/groovy-core type

If there is no new documentation then type


  • check that the files at look OK
  • now change the version number in the project.xml file to be nextReleaseNumber-SNAPSHOT
  • you probbally need to scp the groovy-all-*.jar file to as the release doesn't do this (sad)
  • update JIRA to inform it that a release has been done so that the change log is updated and any pending issues transfer over to the next release
  • maybe create a new JIRA release name for associating pending issues against
  • mail the dev/user lists
  • blog it!
  • have a beer!

In order to make a release, you might also have to define some properties in your file in groovy-core like that:



  • No labels