Release Process

Instructions

• Update the pdf of the online documentation and commit it
• create a temporary release branch and change to it
• Change the release version information
  "files"

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

• commit the change
• Tag with that new release
• Build zips and jars using:
  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:
  (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):
  (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 there is a file ~/.m2/settings.xml containing:
  Where USER and PASSWORD are replaced if the right values.
• Upload the javadocs through rsync to the WebDAV web site (https://dav.codehaus.org/groovy/), for example:
• remove the release branch and push the release tag
• advance the version in your branch in pom.xml and build.properties (don't forget the -SNAPSHOT)
• Update the download links: http://docs.codehaus.org/display/GROOVY/Download
• Announce the release
• Update the release version information to the next snapshot

if the certificate needs an update see: https://docs.codehaus.org/display/HAUSMATES/Installing+a+new+CA+into+the+JDK