Instructions

• Update the pdf of the online documentation and commit it
• Checkout a fresh SVN version
• Change the release version information

  ./build.properties:
      groovyVersion = 1.1-beta-3
  .pom.xml:
      <version>1.1-beta-3</version>

• Tag SVN with that new release

  svn copy https://$user@svn.codehaus.org/groovy/branches/GROOVY_1_5_X/groovy  https://$USER@svn.codehaus.org/groovy/branches/GROOVY_1_5_5 -m "creating branch for 1.5.5 release"

• Build zips and jars using:

  ant dist

  You may need to set ANT_OPTS=-Xmx512m (or similar) if you run out of memory when running GroovyDoc.

• Upload all the zips (but not jars) to the WebDAV distribution site (https://dav.codehaus.org/dist/groovy/distributions), for example, or through rsync if you're authorized:

  rsync -vlogDrzP ./target/dist/*.zip $USER@groovy.codehaus.org:/projects/groovy/dist/

  (just check they are in the right place afterwards; you may still need a webdav client to move them into the right subdirectories if something goes wrong)

• Put m2 jars into right place for uptake into repo1 (see Publishing artifacts on Building Groovy from Source for more details):

  ant -DskipTests=true deploy

  (Note 1: there is currently some duplicated work done by 'ant dist' above and 'ant deploy' here which we need to eventually consolidate)
  
  Should therebe a problem when uploading the jars, check that thre is a file ~/.m2/settings.xml containing:

  <?xml version="1.0"?>
  <settings>
    <servers>
      <server>
        <id>codehaus.org</id>
        <username>USER</username>
        <password>PASSWORD</password>
      </server>
    </servers>
  </settings>

  Where USER and PASSQORD are replaced if the right values.

• Upload the javadocs through rsync to the WebDAV web site, for example:

  rsync -vlogDrzP ./target/html/* $USER@groovy.codehaus.org:/projects/groovy/web/

• Update the download links: http://docs.codehaus.org/display/GROOVY/Download
• Announce the release
• Update the release version information to the next snapshot