Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Tell somebody else about the tag and ask them to check it out and test it!
  2. 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).
  3. Test the built bundle
  4. Test the RPM
  5. Wait a day for other feedback from other testers
  6. 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
    • jetty-j2se6-x.y.z.jar
    • jetty6-all.deb
  7. ONLY WHEN YOU ARE REALLY REALLY REALLY REALLY REALLY SURE EVERYTHING IS REALLY REALLY REALLY OK, then push the maven artifacts:
    No Format
    mvn -DupdateReleaseInfo=true deploy
    cd distribution/jetty-assembly
    mvn -DupdateReleaseInfo=true deploy (site component for jetty-site generation)
    
  8. Update jira to release the version, and enter the next version number
  9. Tell everybody: blogs, lists, etc.
  10. Wait for the bug reports to come in
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