Given that there have been around 50 commits since 1.1-b3, and there are currently 21 Bugzilla issues outstanding, in all honesty, I would find it hard to claim that 1.1-b3 is really a release candidate.
I would prefer to take what we have now, or in a (very) short time from now, and call that a release candidate. Calling 1.1-b3 a release candidate is, in my opinion, tantamount to lowering our standards, or at least appearing to do so in the eyes of our customer base. That is not a good precedent to set. -- Martin Cooper On Fri, 17 Jan 2003, James Turner wrote: > In line with Craig's note earlier tonight, and the semi-voting that is > already going on under another subject, I thought I'd make it > formal/binding. So: > > +1 if you agree that the Struts 1.3b3 release should be declared the > initial release candidate for the 1.1 release, with an RC2 in early > February and final release at the end of February. > > 0 if you have no opinion one way or the other. > > -1 if you believe there is something critical that needs to be done > before we can create a release candidate. > > I believe this requires a lazy majority according to The Rules. > > James Turner > Owner & Manager, Black Bear Software, LLC > [EMAIL PROTECTED] > > Author: > MySQL & JSP Web Applications: > Data Driven Programming Using Tomcat and MySQL > ISBN 0672323095; SAMS, 2002 > > Co-Author: > Struts Kick Start > ISBN 0672324725; SAMS, 2002 > > Forthcoming: > Java Server Faces Kick Start > SAMS, Fall 2003 > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
