Jetty has moved!
Jetty is a project at the Eclipse Foundation.
Homepage:http://www.eclipse.org/jetty
Downloads: http://download.eclipse.org/jetty/
Documentation:http://www.eclipse.org/jetty/documentation/current/
About:http://www.eclipse.org/jetty/about.php
Jetty Powered:http://www.eclipse.org/jetty/powered/
Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
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 7 Next »

Jetty Release Procedures

Currently the release procedure for Jetty is a mostly manual operation:

  1. Verify that there are no blocking issues on the lists or in JIRA.
  2. Update VERSION.txt with the release number and date and commit to trunk.
  3. Create tags in jetty and jetty-contrib repositories with a copy from trunk (or the branch used as a basis for the release):
    svn cp -m 'release x.y.z' https://user@svn.codehaus.org/jetty/jetty/trunk https://user@svn.codehaus.org/jetty/jetty/tags/jetty-x.y.z
    svn cp -m 'release x.y.z' https://user@svn.codehaus.org/jetty-contrib/jetty/trunk https://user@svn.codehaus.org/jetty-contrib/jetty/tags/jetty-x.y.z
    
  4. Checkout tag:
    svn co https://username@svn.codehaus.org/jetty/jetty/tags/jetty-x.y.z
    
  5. Edit svn:externals to include contrib tag:
    cd jetty-x.y.z
    svn propedit svn:externals .  # change trunk to tags/jetty-x.y.z
    rm -fr contrib
    svn up
    
  6. Update the poms and other files to change 6.1-SNAPSHOT to x.y.z:
    bin/change_version.sh x.y.z
    
    The diff in the script will sometimes need to be updated. Recursive
    greps should be done to make sure that all 6.1-SNAPSHOT references have been updated.
  7. Commit the changes to the tag:
    svn commit -m 'release x.y.z'
    svn commit -m 'release x.y.z' contrib
    
  8. build the release
    mvn install
    cd project-website
    mvn install
    cd ..
    
    #build the release bundles:
    bin/build_release_bundles.sh .
    
    This builds a binary and source zip bundle in the parent directory.
    #build additional bundles and jars:
    cd contrib/maven-beanshell-plugin
    mvn install
    cd contrib/rpm
    mvn install
    cd ../jetty-ant
    mvn install
    cd ../../extra/jboss
    mvn -Djboss.home=<your jboss install dir> install
    cd ../..
    
  9. Tell somebody else about the tag and ask them to check it out and test it!
  10. Test the tag yourself in situ (if you need to fix anything you will need to completely clean and go back to first build step).
  11. Test the built bundle
  12. Test the RPM
  13. Wait a day for other feedback from other testers
  14. Create directories in distribution directories and copy artifacts to codehaus (webdav to https://dav.codehaus.org/dist/jetty/ ) and mortbay (scp to mortbay@mortbay.com:/home/ftp/pub/jetty-x.y.z/). The artifacts to upload are:
    • jetty-x.y.z.zip
    • jetty-x.y.z-src.zip
    • jetty-ant-x.y.z.jar
    • jetty6-*-x.y.z.noarch.rpm
    • jetty-x.y.z-jboss-p.q.y.GA-jsp-2.1.sar
  15. ONLY WHEN YOU ARE REALLY REALLY REALLY REALLY REALLY SURE EVERYTHING IS REALLY REALLY REALLY OK, then push the maven artifacts:
    mvn deploy
    
  16. Tell everybody: blogs, lists, etc.
  17. Wait for the bug reports to come in
  • No labels
Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery