OK, I've read over what I proposed again and it looks correct to me. I only made one change after you provided further explanation and that change was to add 'finalized' in the Alpha release description:
+functionality required by the finalised specification and/or significant bugs I did this to further demarcate Milestone releases from Alpha releases. If this sounds good to everyone, I'll push it up. Thanks! On Sat, Sep 17, 2016 at 12:35 PM, Jarosław Górny <jaroslaw.go...@gmail.com> wrote: > 2016-09-16 15:52 GMT+02:00 Mark Thomas <ma...@apache.org>: >> 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? >> > > > Thanks! This is very interesting and important to what I'm doing! > > > -- > Jarosław Górny > > --------------------------------------------------------------------- > 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
