Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E7A5C200B87 for ; Mon, 19 Sep 2016 16:10:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E6487160ACC; Mon, 19 Sep 2016 14:10:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 35D5D160ABC for ; Mon, 19 Sep 2016 16:10:25 +0200 (CEST) Received: (qmail 46758 invoked by uid 500); 19 Sep 2016 14:10:19 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 46735 invoked by uid 99); 19 Sep 2016 14:10:19 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2016 14:10:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 910CD1A02CF for ; Mon, 19 Sep 2016 14:10:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.721 X-Spam-Level: X-Spam-Status: No, score=-0.721 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id SKm1nm2jwXgq for ; Mon, 19 Sep 2016 14:10:17 +0000 (UTC) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com [209.85.215.48]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 2BA9A5F30E for ; Mon, 19 Sep 2016 14:10:17 +0000 (UTC) Received: by mail-lf0-f48.google.com with SMTP id y6so37245021lff.1 for ; Mon, 19 Sep 2016 07:10:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=etsMpn7iICmWYyD1SigLDNZePCGcqoNmV96i3IYHJiQ=; b=WfMd1htz35Ssrof57EvcCDgUR0qEDNGeWil5PNcVEIU6mAjFOoFpNOXK1BlD3h7ZH0 tTV4kmXozptcdNXiHEnJ5Rnwc7yGxZDhmujjUhyY6hfCX2yU9AyVtJ1TH4+EFCwOt3qR nlWcJiCiGpR1jAo4LXZfRjfbc2aA7ngKdc+NCHTBgttaE+K7K5oYlgUl/tW1pvMmCtqR +15EfHIFtEEWcnYQHr/NIZA36Mc4jpWreLN6og44yq6YeFlNZzhbR1uqoiWoswAObx1H 8bniRMtriqkzEQAn87L/eCFN6UoKEII0PCFBsMTbazjhaEluDjzTO9cDlOjbmgh3BjGu oyvA== X-Gm-Message-State: AE9vXwPIZHqUti5Fe+ljS/b7aTZQwnufyUIleahFR5DpQEO0U7p1KbQCpV0GIDOctWpUiOJ/nZRA5rWgA7Bkq9/5 X-Received: by 10.25.15.38 with SMTP id e38mr1280773lfi.24.1474294216305; Mon, 19 Sep 2016 07:10:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.142.81 with HTTP; Mon, 19 Sep 2016 07:10:15 -0700 (PDT) In-Reply-To: References: <03EAFEEF-A199-494C-AC94-84BD650206CB@apache.org> From: Coty Sutherland Date: Mon, 19 Sep 2016 10:10:15 -0400 Message-ID: Subject: Re: Should we update version scheme information for tomcat 9? To: Tomcat Developers List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable archived-at: Mon, 19 Sep 2016 14:10:26 -0000 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 b= ugs 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=C5=82aw G=C3=B3rny wrote: > 2016-09-16 15:52 GMT+02:00 Mark Thomas : >> 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=C5=82aw G=C3=B3rny > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org > For additional commands, e-mail: dev-help@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org