Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 22881 invoked from network); 20 May 2005 16:17:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 May 2005 16:17:20 -0000 Received: (qmail 89595 invoked by uid 500); 20 May 2005 16:17:15 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 89508 invoked by uid 500); 20 May 2005 16:17:14 -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 89482 invoked by uid 99); 20 May 2005 16:17:14 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from Unknown (HELO mgd.gluecode.com) (64.14.202.141) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 20 May 2005 09:17:09 -0700 Received: from [192.168.37.171] (adsl-209-233-18-245.dsl.snfc21.pacbell.net [209.233.18.245]) (authenticated bits=0) by mgd.gluecode.com (8.12.10/8.12.10) with ESMTP id j4KGGVCW003575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 20 May 2005 09:16:31 -0700 Message-ID: <428E0D76.6020408@apache.org> Date: Fri, 20 May 2005 09:16:54 -0700 From: Jeremy Boynes User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: Serialization vs. XML - NOT NOW PLEASE References: <428D6886.10101@apache.org> In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Aaron Mulder wrote: > Need we use all caps for this? It seems kind of impolite. IMO, YES. The discussion has been going on for a week soaking up a lot of time. We've already seen the kernel refactored with no discussion on the list, now we're talking about competing implementations of different mechanisms, kernel rearchitecture, changes in runtime footprint and semantics and so on. Meanwhile, we don't seem be making progress towards certification or the 1.0 release which a lot of people are asking for. WE NEED TO STOP TINKERING AND SHIP A RELEASE. (yes I am shouting) > Also, who is authorized to decide when a discussion "has gone on long enough"? > Well, surely someone who is part of it ;-) > Finally, I disagree. I don't want to just drop the ball for an > indeterminate period of time (or at least, what seems indeterminate to > anyone who's not privy to the TCK testing status). I can understand that > you might not want to actually change the implementation in mid-stream if > it's going to affect the testing process -- but surely we (especially > those of "we" who are not actively TCK testing) can discuss and > investigate some options in the mean time. I promise to call a vote > before making a change that could derail the certification testing. :) > > Thanks, > Aaron > > P.S. My biggest objection to this is really the "after certification" > part, where we're not actually allowed to say how long we think that will > be. > You chose not to participate in that process, I assume because your "availability tends to vary over time." If you have time now to commit to refactoring XML, can you instead help with the certification people are asking for? -- Jeremy