Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 37498 invoked from network); 15 Feb 2008 20:21:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Feb 2008 20:21:31 -0000 Received: (qmail 72349 invoked by uid 500); 15 Feb 2008 20:21:25 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 71922 invoked by uid 500); 15 Feb 2008 20:21:24 -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 71911 invoked by uid 99); 15 Feb 2008 20:21:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2008 12:21:24 -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: domain of eljotpl@gmail.com designates 64.233.166.176 as permitted sender) Received: from [64.233.166.176] (HELO py-out-1112.google.com) (64.233.166.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2008 20:20:50 +0000 Received: by py-out-1112.google.com with SMTP id a25so1003665pyi.11 for ; Fri, 15 Feb 2008 12:20:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=ZDzm/V7wlL1+l6SCkbzs+/HXkRlgDvoHoFSMk3waS34=; b=dg56NNXEaB6VqHlvW5IMLtbJfyjcywUK2x+0B2ZfJQ/zv16elwdKu5IOHGJT7NNMGSE/7Mczc/skwsQzvQn8/B5DXrXBLNiPzQKxNvSH1xejCsjAhzkuyQsmoVX5MRS+ajY/99k3Ll9ig9FJc2Um8Uy7Aw+B0OyAEx7p25zE9U8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=D6nol8GypvDDBunKojTOW/MOoQ2tJekNjSKIVeyL1aNiC0um4KvcCDcZmLkQfhGzYTdqOnJlDlN6hnxBimn+EHgi/o2C9pWMnw9Va2hnoSUTw+5LhmPr/sn0Kq/5WHMwxjm+piBuiVd3VCID05FgYVfxlaDxoTp6soXflOrL/C4= Received: by 10.35.67.18 with SMTP id u18mr3376242pyk.64.1203106858479; Fri, 15 Feb 2008 12:20:58 -0800 (PST) Received: by 10.35.44.20 with HTTP; Fri, 15 Feb 2008 12:20:58 -0800 (PST) Message-ID: <1b5bfeb50802151220i2c962391hdaabec17beec0f2d@mail.gmail.com> Date: Fri, 15 Feb 2008 12:20:58 -0800 From: "Jacek Laskowski" Reply-To: jacek@laskowski.net.pl Sender: eljotpl@gmail.com To: dev@geronimo.apache.org Subject: Re: [DISCUSS] Geronimo Server 2.1 and Geronimo TxManager 2.1.1 Releases In-Reply-To: <5eb405c70802150846q62bbb1eek44560a71a1e412d9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47B077C9.6060809@earthlink.net> <47B467C0.2090103@earthlink.net> <1b5bfeb50802141030j6b1af890v84f88a8b6af8e30c@mail.gmail.com> <5eb405c70802150712y618f149gfe2d8051b59b0dd0@mail.gmail.com> <35A675BC-FDEC-4533-A399-14E775254FB5@gmail.com> <5eb405c70802150846q62bbb1eek44560a71a1e412d9@mail.gmail.com> X-Google-Sender-Auth: 65feac7febf900ec X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Feb 15, 2008 at 8:46 AM, Jarek Gawor wrote: > But, IMHO, this is not just a bug it is a major bug where one of the > important pieces of Geronimo functionality is simply not working on > port 8443. Personally, I would have voted -1 on the release if I > realized the full scope of this bug sooner. But maybe that's just me.. > so I would like to know what other people think about this problem. If > it's just me, that's fine. If not, maybe we should consider > withdrawing the release. Although the admin console is working fine on > port 8080 and maybe that's good enough. I'd not withdraw it. It's what we've got and no matter how beautiful it is - that's how it is now. We could never release Geronimo as there're always bugs. Some important, some not, but since we're all for releasing often I'm for leaving it as it is now and put a note in the RELEASE_NOTES about it. We can work it out in 2.1.1. I just think it's time for 2.1 and see people what we've got so they can see its value. There're other bugs lurking, and 2.1 release will let them show up. I'm still +1 for 2.1. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl