Going from Alpha/Beta to GA is no different than going from RC to Final. A belief that the distribution has been widely tested and an absence of problem reports.
I doubt that we'd have the courage to promote 1.2.1 from Alpha to GA, but if some minor issues were found and fixed in a 1.2.1 beta, we might want to take a 1.2.2 from Alpha direct to GA. Of course, I'd prefer that 1.2.1 went from Beta to GA, if it merits that lofty status :) -Ted. <<... leaving on that midnight train to Georgia ...>> On Fri, 09 Jul 2004 09:48:02 -0500, Joe Germuska wrote: >�+1 �for beta; I've plugged 1.2.1 into an app which in in another >�dev cycle and so should be able to give it a pretty good workout. >�Not quite sure what our threshold for GA is... a certain time >�period? Sworn testimonials? �A sign from above? > >�Joe > >�At 10:47 AM -0400 7/8/04, Ted Husted wrote: >>�The repository is tagged for STRUTS_1_2_1, and the release is >>�available for review at >> >>�* http://www.apache.org/~husted/struts/v1.2.1 >> >>�Once you have had a chance to review the release, please respond >>�as to whether we should >>�[ ] Keep this release at Alpha. Followup reports filed to >>�Bugzilla. >> >>�[* ] Promote this release to Beta and announce on Struts User for >>�further testing >> >>�[ ] Promote this release to General Availability now (*) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
