As Joe mentioned, we no longer use the "beta-beta-beta-final" versioning scheme.
We now use an "immutable" versioning scheme, like that used by the Apache HTTPD project, Jakata Tomcat, and many others. Each release is a "point" release, meaning it's a three part number: major-minor-point. The most recent Struts point release is 1.2.0. The next will be 1.2.1. Each number is an integer, so there can be any number of point releases. Each point release is created exactly once. After the release is created, we vote as to whether to change its status from "alpha" to "beta" and/or "general availability". We may also vote to demote a release, if we discover problems later. At this time, Struts 1.1 is the best available release. Struts 1.2.0 is also available, but still considered "alpha" quality. ** We encourage everyone to try running your applications against 1.2.0 and report any problems. ** Right now, there are a handful of problem tickets against 1.2.0. As soon as those are resolved, we will issue 1.2.1. Hopefully, that release will make "GA" status. Either way, the next 1.2.x release after 1.2.1 will be 1.2.2. -Ted. On Sat, 20 Mar 2004 23:20:39 +0200, Erez Efrati wrote: > Yes, I here so much of this version so I wondered if it was > released or the CVS head version is stable enough for production. > > Erez > > > -----Original Message----- > From: Zsolt Koppany [mailto:[EMAIL PROTECTED] Sent: > Saturday, March 20, 2004 10:58 PM To: Struts Users Mailing List > Subject: RE: version 1.2 > > Hi, > > > do you mean struts-1.2 final? I cannot find that at: > http://jakarta.apache.org/site/binindex.cgi > > Zsolt > > >> -----Original Message----- >> From: Joe Germuska [mailto:[EMAIL PROTECTED] >> Sent: Saturday, March 20, 2004 3:20 PM >> To: Struts Users Mailing List >> Subject: Re: version 1.2 >> >> >> At 1:14 PM +0200 3/20/04, Erez Efrati wrote: >>> Hi, I am currently working with the 1.1, is there a good reason >>> to >>> > move >>> to 1.2? Is it going to be released sometime soon? >>> >> >> Struts 1.2.0 was released a few weeks ago using the new Tomcat- >> style version numbering. That means that a numbered release may >> or may not be considered a production quality release. There has >> not been a formal vote on the status of 1.2.0, but I think we'd >> cut another release rather than vote 1.2.0 as production-quality. >> >> If you're satisfied with Struts 1.1, you may as well stick with >> it. If you like to keep up with Struts while its evolving, you >> might be just as well off building from CVS Head as using Struts >> 1.2.0. That way you'd roll in recent bug fixes and be in a >> position to fix other bugs yourself if you find them (or just >> update from CVS and apply fixes and changes as they come in.) >> >> There aren't anywhere near the number of structural changes >> between 1.1 and 1.2 that there were between 1.0 and 1.1. Many >> deprecated members from 1.1 have been removed, so if you were >> ignoring the deprecation warnings all this time, you'll finally >> have to catch up. Also, if I recall correctly, there are some >> changes in the JSP tag libraries that may be hard to find until >> you compile the JSPs. >> >> Hope that helps, >> Joe >> >> >> -- >> Joe Germuska >> [EMAIL PROTECTED] >> http://blog.germuska.com >> "Imagine if every Thursday your shoes exploded if you tied them >> the usual way. This happens to us all the time with computers, >> and nobody thinks of complaining." -- Jef Raskin >> >> ------------------------------------------------------------------ >> --- To unsubscribe, e-mail: struts-user- >> [EMAIL PROTECTED] For additional commands, e-mail: >> [EMAIL PROTECTED] > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: struts-user- > [EMAIL PROTECTED] For additional commands, e-mail: > [EMAIL PROTECTED] > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: struts-user- > [EMAIL PROTECTED] For additional commands, e-mail: > [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
