Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 98677 invoked from network); 17 Apr 2006 11:30:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Apr 2006 11:30:30 -0000 Received: (qmail 90850 invoked by uid 500); 17 Apr 2006 11:30:29 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 90274 invoked by uid 500); 17 Apr 2006 11:30:27 -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 90259 invoked by uid 99); 17 Apr 2006 11:30:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Apr 2006 04:30:26 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=RCVD_IN_SORBS_WEB,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [63.208.196.171] (HELO outbound.mailhop.org) (63.208.196.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Apr 2006 04:30:25 -0700 Received: from bi01p1.nc.us.ibm.com ([129.33.49.251] helo=[9.27.40.109]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1FVRvf-0009WW-UM for dev@geronimo.apache.org; Mon, 17 Apr 2006 07:30:03 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 129.33.49.251 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: hogndos Message-ID: <44437C3A.8030108@hogstrom.org> Date: Mon, 17 Apr 2006 07:30:02 -0400 From: Matt Hogstrom User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: 1.1 Release (Version Upgrades) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N We're nearing the end of the CTS cycle and will soon have a stable 1.1. Once we reach this critical stage we need to move into the final stages to release 1.1. Here is my proposed list. *Starting now:* 1. Code freeze for 2006/04/18 23:59 PST (except bug and performance fixes) *Once we've reached CTS stable:* (feel free to volunteer for tasks) 1. Begin changing packages to upgrade as appropriate (proposed list below) 2. Develop *Release Notes* 3. Draft a *Press Release* 4. Begin performance regression 5. SWAG a date Release Candidate 6. Test, Test, Test *After 1.1 is stable:* 1. Formalize strategy for syncing 1.1 and HEAD 2. Define a set of release goals for 1.2 and propose a target date I suggest that we define a theme for a release to help the group focus on a set of goals that will guide the work for the next release. This is not intended to be a rigid constraint but merely to provide some direction. It will also help us define a target release date to help us deliver on a consistent schedule for our users. 3. Solicit user feedback for prioritizing work Listening to our users and providing them with the features they want. 4. Aggressively update our dependent package versions to new new levels. Cheers, Matt *Version Upgrades - Matt's Suggestions* I looked at the packages out there and here is the first stab at which ones we should upgrade. Comments? *G* *Available* *Version* *Package* *Version* *Version* 1.1 activemq 3.2.1 3.2.3 1.1 castor 0.9.5.3 0.9.9.1 or 1.0M3 1.1 daytrader 1.1-SNAPSHOT 1.1-SNAPSHOT 1.1 derby 10.0.2.1 10.1.2.1 1.1 derby 10.1.1.0 10.1.2.1 1.1 jasper 5.5.9 5.5.15 1.1 jasper 5.5.12 5.5.15 1.1 jetty 5.1.9 5.1.10 1.1 openejb 2.1-SNAPSHOT 2.1-SNAPSHOT 1.1 stax 1.1.1-dev 1.1.2 1.1 tomcat 5.5.9 5.5.15 1.1 tomcat_ajp 5.5.9 5.5.15 1.1 tranql 1.2.1 1.3-SNAPSHOT 1.1 tranql_connector 1.1 1.2-SNAPSHOT