[Openjnlp-devel] A new version wants to be released

[Kevin H. <ke...@na...>]

OpenJNLP has gone too long without a release. More importantly, there 
are major improvements to OpenJNLP that should have been released 
already (e.g., applet support and the new launcher).

I don't think the current code base is quite ready for a release, but I 
want to do a feature freeze on it. My thinking is that instead of 
stopping work on the main cvs trunk releases should now be branches. 
This will allow work to continue on new features without interrupting 
the release code base. When changes are made on the release branch they 
can be merged back into the main trunk.

This approach is based on my (vast?) cvs experience over the years and 
the good advice from the very good book, "Open Source Development with 
CVS". It happens to be (mostly) free at <http://cvsbook.red-bean.com/>. 
Definately worth a read. The free chapters are the ones that cover the 
mechanics of using CVS.