On 16/09/2016 13:59, Coty Sutherland wrote: > I'm not sure where to file a bug for this, but I produced a first pass > at a patch to update the page. I'm not sure I have a solid grasp on > why we're doing milestones in tc9 (other than to prevent a bunch of > revisions from being releases pre-beta) so this might need some > changes to convey the intent a bit better.
Version numbers aren't the concern. Think of it as: - Milestone - Specification JARs not complete - Alpha - Specification JARs complete, other stuff (including the implementation of the specification) not complete - Beta - Feature complete, not production ready - Stable - Production ready Once the spec is final getting to Alpha is pretty easy. Historically, we haven't been this far ahead of the curve before. We've usually been playing catch up so we've started with Alpha. Does that help? Mark > > On Thu, Sep 15, 2016 at 12:26 PM, Mark Thomas <ma...@apache.org> wrote: >> On 15 September 2016 16:32:36 BST, Coty Sutherland <csuth...@redhat.com> >> wrote: >>> Hi all, >>> >>> I'm getting quite a few questions on freenode in #tomcat about the >>> versioning scheme for tomcat 9. I looked at the >>> http://tomcat.apache.org/whichversion.html page and it has some good >>> information there, but it doesn't mention what the milestone releases >>> are or how they fit into the alpha/beta/stable releases. Can we add >>> some information there to help users better understand the milestone >>> releases (if that is going to continue to be a thing) and how they fit >>> into the lifecycle? >>> >>> I can open a bug for it, but wanted to get an opinion on whether or >>> not this is something that we want to do. >>> >>> >>> >>> Thanks, >>> Coty >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: dev-h...@tomcat.apache.org >> >> +1 >> >> Current plan is milestones until the specs are final. Depending on what >> happens with JavaEE 7 we might need to rethink that. We should know more >> after Java One. >> >> Mark >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org