Don Brown wrote:
If that's the case, I really want to start kicking 1.x releases out the
door. What can I do to help?
The big stumbling block was that some of the tests weren't running. If
they've been fixed, then anyone could cut a release when they felt the
code base was ready. Like, say, now.
Ok, so we are moving to a Tomcat-style release numbering. How exactly do
we make it clear that 1.2.0 will be "beta quality" while another in
the 1.2.x line will be GA quality. One advantage of alpha, beta, and rc
qualifiers is it is immediately obvious to users which one is which. I
think tomcat
We can just label them as such on the release page.
http://jakarta.apache.org/site/binindex.cgi
This is a free-form page, and we can label the links anyway we like
* Struts 1.1.0 - Best available version
* Struts 1.2.0 - Also available ("Beta" quality release)
later ...
* Struts 1.2.6 - Best av
