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.
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 >
Index: docs/whichversion.html =================================================================== --- docs/whichversion.html (revision 1761025) +++ docs/whichversion.html (working copy) @@ -397,22 +397,23 @@ </div> -<h3 id="Alpha_/_Beta_/_Stable">Alpha / Beta / Stable</h3> +<h3 id="Milestone_/_Alpha_/_Beta_/_Stable">Milestone / Alpha / Beta / Stable</h3> <div class="text"> <p>When voting for a release, reviewers specify the stability level that they consider the release has reached. Initial releases of a new major version -typically process from Alpha, through Beta to Stable over a period of several -months. However, the Stable level is only available once the Java specifications -the release implements have been finalised. This means a release that in all -other respects is considered stable, may still be labelled as Beta if the -specifications are not final.</p> +may have Milestone releases (depending on the state of the specification) before +moving into Alpha state and then typically process from Alpha, through Beta to +Stable over a period of several months. However, the Stable level is only +available once the Java specifications the release implements have been finalised. +This means a release that in all other respects is considered stable, may still +be labelled as Beta if the specifications are not final.</p> <p>The download pages will always show the latest stable release and any newer -Alpha or Beta release if one exists. Alpha and beta releases are always clearly -marked on the download pages.</p> +Milestone, Alpha, or Beta release if one exists. Milestone, Alpha, and Beta +releases are always clearly marked on the download pages.</p> <p>Stability is a subjective judgement and you should always read carefully the @@ -423,6 +424,11 @@ <p> +<strong>Milestone</strong> releases may contain large amounts of untested/missing +functionality that is being implemented based on an unfinished specification and +therefore could change significantly as the specification changes.</p> + +<p> <strong>Alpha</strong> releases may contain large amounts of untested/missing functionality required by the specification and/or significant bugs and are not expected to run stably for any length of time.</p>
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
