Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 30279 invoked from network); 11 Oct 2010 04:02:08 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Oct 2010 04:02:08 -0000 Received: (qmail 76999 invoked by uid 500); 11 Oct 2010 04:02:08 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 76910 invoked by uid 500); 11 Oct 2010 04:02:05 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 76903 invoked by uid 99); 11 Oct 2010 04:02:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Oct 2010 04:02:05 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rwonly@gmail.com designates 74.125.82.50 as permitted sender) Received: from [74.125.82.50] (HELO mail-ww0-f50.google.com) (74.125.82.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Oct 2010 04:01:57 +0000 Received: by wwb13 with SMTP id 13so15539wwb.31 for ; Sun, 10 Oct 2010 21:01:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=nWMA5jv0rSHJaVMahiaU5gnTvys+hhqBUEghc5+miJw=; b=KwM5knli8drtjMbYwBFQnOZ9c4/kPjvKnWDMd5swSJLBul/FC91rCZ5EV3iFcz3BvA H7Tasv0tbBkJZ1d2DGBY/0pN5zHh0/Pfvw9/gsrNawQY6wV2Y/34RvCiQWADdkJrr6YG HWLitkhrjq/6R0LXWfIik/nVdAfLu3d09Vmog= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=shBLkY+jXRGxQhW+bKmy98Ebf/Iuur6BHJdcN4kpy4LRgMUW72d0lYNRdC7DnT4rGo 1WyLHbB2aado/TPuQR5iNCi0sm5w3HEkjpsoMOoJJB1sgU0d/Gpp+SqHNaabhI3k01NA qKug/jbRcWvSB2BgMKFVZU6fhXaAyQeIZoD1Y= Received: by 10.216.188.209 with SMTP id a59mr3194318wen.87.1286769393221; Sun, 10 Oct 2010 20:56:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.184.12 with HTTP; Sun, 10 Oct 2010 20:56:13 -0700 (PDT) In-Reply-To: References: From: Rex Wang Date: Mon, 11 Oct 2010 11:56:13 +0800 Message-ID: Subject: Fwd: [taglibs] Release for 1.2, was: The status of tomcat taglibs project? To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=0016364d1bd797405304924f58a1 X-Virus-Checked: Checked by ClamAV on apache.org --0016364d1bd797405304924f58a1 Content-Type: text/plain; charset=ISO-8859-1 FYI, Finally, Tomcat community decides to make a release of the standard taglib. -Rex ---------- Forwarded message ---------- From: Jeremy Boynes Date: 2010/10/10 Subject: [taglibs] Release for 1.2, was: The status of tomcat taglibs project? To: Tomcat Developers List On Oct 9, 2010, at 12:37 AM, Rex Wang wrote: > > 2. When do you plan to make the first release? Our project really wants to > switch to the open source implementation.. Trunk now passes the JSTL1.2 TCK so we can release when we want to. However, there have already been some large changes in the 1.2 stream (such as the move to the Tomcat project, using a 1.5 runtime, switching to Maven build) that will be visible to users so if we are going to make any others my vote would be to do that before releasing 1.2.0 so they are only impacted once; examples of these are: * using a different XPath implementation to fix the performance issues with the XML tags (changes dependencies) * splitting out the 1.0 compatibility support into a different artifact * clean-up on the Maven POMs (especially any changes that impact the parent POM) We may also need to revise the release process based on the move to the Tomcat project and Maven build. With that in mind, what do people think about shooting for a release towards the end of the month? -- Lei Wang (Rex) rwonly AT apache.org --0016364d1bd797405304924f58a1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable FYI,

Finally, Tomcat community decides to make a release of the stan= dard taglib.

-Rex

---------- Forwa= rded message ----------
From: Jeremy Boyne= s <jboynes@apache.org>
Date: 2010/10/10
Subject: [taglibs] Release for 1.2, was: The status of = tomcat taglibs project?
To: Tomcat Developers List <dev@tomcat.apache.org>


On Oct 9, 2010, at 12:37 AM, Rex Wang wrote:
>
> 2. When do you plan to make the first release? Our project really want= s to
> switch to the open source implementation..

Trunk now passes the JSTL1.2 TCK so we can release when we want to. However= , there have already been some large changes in the 1.2 stream (such as the= move to the Tomcat project, using a 1.5 runtime, switching to Maven build)= that will be visible to users so if we are going to make any others my vot= e would be to do that before releasing 1.2.0 so they are only impacted once= ; examples of these are:

* using a different XPath implementation to fix the performance issues with= the XML tags (changes dependencies)
* splitting out the 1.0 compatibility support into a different artifact
* clean-up on the Maven POMs (especially any changes that impact the parent= POM)

We may also need to revise the release process based on the move to the Tom= cat project and Maven build.

With that in mind, what do people think about shooting for a release toward= s the end of the month?



--
Lei Wang (Rex= )
rwonly AT apache.org
--0016364d1bd797405304924f58a1--