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

NOTE: please also use jdk1.4 to build the jboss sar, as this will use jsp-2.0, which some versions of jboss seem to need in order to run it's web console correctly.

Tell somebody else about the tag and ask them to check it out and test it!

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).

Test the built bundle

Test the RPM

Wait a day for other feedback from other testers

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

ONLY WHEN YOU ARE REALLY REALLY REALLY REALLY REALLY SURE EVERYTHING IS REALLY REALLY REALLY OK, then push the maven artifacts:

mvn deploy

Tell everybody: blogs, lists, etc.

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