I believe to get it ready for "prime time" as a General Availability release will mainly be a matter of updating the documentation. But, the best way to generate some interest in doing that may be to publish a milestone release.
Also, to make the GA grade, all dependent libraries would also have to be GA grade. From what Rob says, we want to use the latest Validator build now. So, a Commons-Validator 1.0.3 release would help in that regard.
-Ted.
Tim Chen wrote:
What would need to be done to get it to "milestone" -Tim
Ted Husted wrote:
With the long weekend coming up, I was thinking of rolling up my sleeves and doing whatever needs to be done to cut 1.2.0.
Anyone one aware of any serious showstoppers?
While under the current scheme, any release has the potential to make the General Availability grade, I would anticipate that 1.2.0 will end up being a simple "milestone" release, and we'll have to cut a few more before we get to GA. But, I'd like to start the ball rolling.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ted Husted, Junit in Action - <http://www.manning.com/massol/>, Struts in Action - <http://husted.com/struts/book.html>, JSP Site Design - <http://www.amazon.com/exec/obidos/ISBN=1861005512>.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
