Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 53732 invoked from network); 2 Dec 2008 16:55:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Dec 2008 16:55:11 -0000 Received: (qmail 70313 invoked by uid 500); 2 Dec 2008 16:55:21 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 70264 invoked by uid 500); 2 Dec 2008 16:55:21 -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 70253 invoked by uid 99); 2 Dec 2008 16:55:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2008 08:55:21 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [209.86.89.69] (HELO elasmtp-mealy.atl.sa.earthlink.net) (209.86.89.69) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2008 16:53:52 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Gkn6SDBL9qTtApXRMnqlMXZ1vRpY5oa6n8U4TlCk7OLEZM54AVkKuHLlv+dWTaAW; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [129.33.49.251] (helo=dyn9-37-243-139.raleigh.ibm.com) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1L7YVx-0004b7-Uw for dev@geronimo.apache.org; Tue, 02 Dec 2008 11:54:22 -0500 Message-ID: <49356824.8040602@earthlink.net> Date: Tue, 02 Dec 2008 11:53:56 -0500 From: Joe Bohn User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: 2.2 (trunk) bucket-o-snapshots References: <491A0F62.3020805@earthlink.net> <5eb405c70811132224r6c2fc6d7m9ca507f30f05b9c1@mail.gmail.com> In-Reply-To: <5eb405c70811132224r6c2fc6d7m9ca507f30f05b9c1@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: c408501814fc19611aa676d7e74259b7b3291a7d08dfec790180e430eeef5941d5fd080d265f8485350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 129.33.49.251 X-Virus-Checked: Checked by ClamAV on apache.org Hi Jarek, It looks like the Axis2 1.5 release didn't happen yet. Is there a new target? Also, my offer still stands to help with the concurrent spec release if you want. Let me know. Thanks, Joe Jarek Gawor wrote: > Axiom, XmlSchema, and Woden are all dependencies of Axis2. There is a > plan for Axis2 release at the end of this month but I'm not sure if > it's going to happen with all these dependencies. So getting Axis2 > release might be an issue to us. > > As to geronimo-concurrent_1.0_spec 1.0-SNAPSHOT, we can get that > released now. I have no pending updates for it. > > Jarek > > On Tue, Nov 11, 2008 at 6:04 PM, Joe Bohn wrote: >> It has been mentioned several times that we should be looking to release >> Geronimo 2.2 before the end of the year (preferrably mid-December). >> >> >> Before we can consider a release there are a large number of snapshots that >> need to be removed/replaced in our project. Can anybody shed any light on >> these (or others that I may have missed)? >> >> >> OpenEJB 3.1-SNAPSHOT - Actually, OpenEJB 3.1 was released in late October. >> However, the trunk version was never updated and some additional changes >> have been included. Recent changes in Geronimo trunk now require this >> snapshot that is actually newer than the 3.1 release. IMO we should revert >> the trunk change and attempt to work with the released OpenEJB 3.1. >> >> Axis2 SNAPSHOT (yep, it's just SNAPSHOT without a number). IIUC correctly >> we need to get an Axis2 release before we can consider a Geronimo 2.2 >> release. Does anybody know how close we are to getting an Axis2 release? >> >> Axiom SNAPSHOT (yep. it's just SNAPSHOT too). I believe this is required by >> Axis2 ... so if Axis2 is released then they will have to get Axiom released >> as well (and we can pick up the released version). >> >> -xBean 3.5-SNAPSHOT. Is this snapshot really required (I presume it must >> be)? In branches/2.1 we're still using 3.3. It looks like the latest >> released version is 3.4.3. I'll give that a shot if I don't hear from >> anybody that we really need 3.5. >> >> -wadi 2.1-SNAPSHOT. Is this snapshot really required (I presume it must >> be)? In branches/2.1 we're using 2.0. What function requires 2.1-SNAPSHOT >> and is can somebody directly involved with wadi provide an estimate on when >> this might be released? >> >> -geronimo_j2ee-connector_1.6_spec 1.0-EA-SNAPSHOT. Are we at a point where >> we can release this spec or do we need to wait until we verify tck? >> >> - geronimo-jaspi_1.0_spec 1.0-SNAPSHOT. Are we at a point where we can >> release this spec or do we need to wait until we verify tck? >> >> - geronimo-servlet_3.0_spec 1.0-EA-SNAPSHOT. Are we at a point where we can >> release this spec or do we need to wait until we verify tck? >> >> - geronimo-jaspi 1.0-SNAPSHOT. This is a new geronimo component. How close >> is this to being able to be released? >> >> - geronimo-concurrent_1.0_spec 1.0-SNAPSHOT. How close is this to being >> able to be released? >> >> - XmlSchema SNAPSHOT (yep, it's just SNAPSHOT). I believe this is also >> related to Axis2 dependencies and will have to be resolved by Axis2 as they >> release. >> >> - woden* 1.0-SNAPSHOT. This is also related to Axis2 and will have to be >> resolved for an Axis2 release so we will pull in whatever they require. >> >> - selenium-maven-plugin 1.0-rc-1-SNAPSHOT. I believe that we pulled this in >> trying to resolve the FF3 issues. It's not clear to me if we would have to >> remove this SNAPSHOT prior to a release but I think it would be best to >> ensure that the tagged release can always be built and run with tests - >> therefore I think we should remove it. Any other opinions? >> >> - jspc-maven-plugin 2.0-alpha-2-SNAPSHOT. I'm not sure why this is updated >> (in branches/2.1 we use 2.0-alpha-1-20070806). Anybody know? We should >> remove it. >> >> - jspc-compiler-tomcat6 2.0-alpha-2-SNAPSHOT. I'm not sure why this was >> updated either. In branches/2.1 we updated the maven plugin (above) but not >> the compiler but in trunk both were updated to the alpha-2-SNAPSHOT. >> Anybody know why? >> >> - ianal-maven-plugin 1.0-alpha-1-SNAPSHOT. No doubt to support the new >> legal file processing. Is there a released version we can use instead of >> the SNAPSHOT or do we need to get a release here are well? >> >> >> Joe >> >