GuideLines For Committers

As we prepare for cutting a release, we need to get JIRA cleaned up and populated with enough data to generate release notes and give people an idea of what is here and what is to come in future releases.

All Committers, please:

Update any open items in JIRA. Close anything no longer relavent to the current state of Geronimo or related components (Jetty, OpenEJB).
Add a couple 'New Feature' items on what is supported in anything you wrote. Use "New Feature" as the issue type and "1.0M1" in the 'Affects Versions' and 'Fix Versions' sections.
Add as many 'Task' items as you can think of for what is not yet supported or implemented in any code you worked on. Use "Task" as the issue type and "1.0M1" in the 'Affects Versions' section.

Of all these, number 3 is the most critical; we want to give users as much information on what is not there so they don't spend forever trying to get it work.

We don't want people missinformed on what is not supported and implemented and frustrated with us because they had to learn the hard way.
We do want people to download Geronimo and give us feedback on what we say should work, but does not.

Number 2 will never happen if people get bit by number 1.

Publishing unstable builds (i.e. unofficial releases)

David Blevins created this script quite a while ago and just want to let the committers know how to run it. It's really easy, just run:

 $ wget http://svn.apache.org/repos/asf/geronimo/scripts/publish_build.sh && bash publish_build.sh

That downloads the script and executes it.

You need:

Any system with bash 2.05b
SSH keys setup at apache.org
svn, cvs, wget, zip, tar, perl, openssl
jdk 1.4.x
Maven 1.x

Here are a few examples of using it:

./publish_build.sh 
./publish_build.sh somewhere.com
./publish_build.sh joe@somewhere.com
./publish_build.sh somewhere.com /some/dir