The idea is that we are doing them in tandem. We rolled Validator 1.1.3, so now can roll Struts 1.2.1. Once a <noun>release</noun> is rolled, then we decide whether to <verb>release</verb> it as beta or stable/General Availability. The votes are not final, so we can vote them to beta and then to stable after community review and testing.
The advantage of the current system is that we can change the status of a release without rolling it again. So, if Validator 1.1.3 goes stable, then Struts 1.2.1 could follow suit, and we would not have to touch the distribution. -Ted. On Tue, 06 Jul 2004 08:00:44 -0500, 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?. 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.1 > > Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
