How to release stuff

This is fairly basic stuff, but still seems to be a complete mystery to 
a large number of people, so I'll spell it out as best I understand it. 
Feel free to submit corrections. The steps below all need to happen, 
you can use your creativity in picking the order in which you do them.

- Upload a dist zip/jar/src to java.net
- Update documentation
- Update the website
- Post a release note in a number of places. Homepage of os.com as a 
bare minimum

Reason for this reminder? The astounding 'release' of oscore 2.2.4. God 
knows what happened to 2.2.3. Needless to say, the download links were 
broken, the website was not updated. It took a java.net admin to 
contact us and point out that we're so incompetent we're unable to have 
our own website point to our own project downloads.

If you don't have the time to do these things, then don't bother. No 
release is much better than a half assed release. While I realise this 
is a hobby and a fun thing, there's no reason why it can't be 
professional and a source of pride too. None of us would (or should) 
get away with shipping a final version product and saying 'oh, it's 
missing these chunks but I'll send them over tomorrow' in the real 
world, so let's apply that same quality control to opensymphony!

Hani



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click