Milestones imply a series of goals to be met, not just when we feel like it, or every Tuesday. To be a milestone, there need to some objective criteria that everyone can agree have been met.
Don't get me wrong, I like frequent builds, I just hate to see a useful release engineering term get debased. Remy Maucherat wrote: > Hi, > > First, a simple vote about the version numbering scheme for Tomcat 5.0. > I think the method used for Tomcat 4.1.x is working well and promotes > quality, although it certainly delayed the apprition of a stable build > of Tomcat 4.1. > I propose keeping it for Tomcat 5.0. > > <ballot> > +1 [ ] Tomcat 5 should use Tomcat 4.1 version numbering scheme and > release management > -1 [ ] Tomcat 5 should use something else (to be decided later) > </ballot> > > Although Tomcat 5 is still far from being feature complete (and won't > be in stable form until the servlet & JSP specs ship, at the > earliest), it could make sense to start releasing test milestones. The > build process works, and the binary works (to some extent; of course, > many features are missing and many refactorings still need to be made). > > The milestones will have a 5.0.x number, similar to the current 4.1.x > releases. > > <ballot> > +1 [ ] Start releasing milestones for Tomcat 5.0 on a regular basis soon > -1 [ ] No, later > </ballot> > > Remy > > > -- > 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]>
