The users of struts can understand 1.2.1 w/o 1.2.0, most of use are also using tomcat as well and most of us skip releases. If it takes extra time for no other benefit than to keep things neet, it is probably not worth the effort.
Edgar > -----Original Message----- > From: Steve Raeburn [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 09, 2003 11:12 PM > To: 'Struts Developers List' > Subject: RE: When is the next release? > > > > > -----Original Message----- > > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] > > Sent: August 9, 2003 8:57 PM > > To: Struts Developers List > > Subject: Re: When is the next release? > > > > That was my understanding as well -- we agreed to switch to > the x.y.z > > style that Apache HTTPD and Tomcat are using, where you > post the bits > > and then call for a vote on stability (alpha/beta/general > > availability). It's perfectly reasonable to have a series > of "general > > availability" releases with new features in the 1.2.x > series, as long > > as we continue to maintain backwards compatibility within it. > > > > Therefore the first release would be 1.2.1 and we'd keep going from > > there. > > I think it would be strange to go directly to a 1.2.1 > release, which I suspect is why Ted was talking about a beta. > Tomcat has a 4_1_0 tag in CVS, but I don't know if that was > released as such. > > It's not my intention to reopen an old discussion, but I > would like to confirm exactly what version this will be. > > Steve > > > > > > > Craig > > > > > > --------------------------------------------------------------------- > 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]
