Joe Germuska wrote:
This is a Chicken and an an Egg situation. Not enough people use Validator standalone for it to be promoted. Validator 1.1.3 only works with a nightly build of Struts. So to get the required number of users Validator will need in a released version of Struts to get the testing it needs to be promoted.
Isn't this one of the benefits of the new release scheme that both projects use?.
It's a two-edged sword.
If we always build nightlies from CVS-HEAD of the dependencies (which is essentially what Gump does), nobody ever has the chance to test the particular combination of JARs that we're actually going to include in the release. Now, we can at least say "please treat nightly build YYYYMMDD as a release candidate for Struts 1.2.1, and test it", with some assurance that the bits being tested actually represent what we'll actually ship.
I would be -1 on voting to call Struts 1.2.1 "General Availability" if we couldn't call Validator 1.1.3 "General Availability" -- but that isn't the same as being -1 on *releasing* Struts 1.2.1The post-release vote on quality of a Struts release is just that ... a vote on its quality. But we wouldn't have the option to call 1.2.1 "suitable for GA" if Validator (or any other component) wasn't final yet, even if the quality was sufficient -- so I don't think we should even release it that way.
At any rate, I've seen lots of assurances in my catching up on mail that Validator 1.1.3 will-be/has-been released, so it should just be a short matter of time.
Joe
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
