Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 87293 invoked from network); 16 Mar 2011 19:42:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Mar 2011 19:42:47 -0000 Received: (qmail 10513 invoked by uid 500); 16 Mar 2011 19:42:47 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 10475 invoked by uid 500); 16 Mar 2011 19:42:47 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 10468 invoked by uid 99); 16 Mar 2011 19:42:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Mar 2011 19:42:47 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [148.87.113.121] (HELO rcsinet10.oracle.com) (148.87.113.121) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Mar 2011 19:42:38 +0000 Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p2GJgGoQ001805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 16 Mar 2011 19:42:17 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p2GJgFAR012630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 16 Mar 2011 19:42:16 GMT Received: from abhmt018.oracle.com (abhmt018.oracle.com [141.146.116.27]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p2GJgFE9019218 for ; Wed, 16 Mar 2011 14:42:15 -0500 Received: from localhost (/10.175.2.77) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 16 Mar 2011 12:42:14 -0700 From: Knut Anders Hatlen To: derby-dev@db.apache.org Subject: Re: opinions on a less aggressive release of the istats feature? References: <4D7AB760.8050209@sbcglobal.net> <4D7ABDA6.6070109@oracle.com> <4D7E0DDE.2000709@oracle.com> <97EB699F861AD841B5908C7CA9C9565601607A209053@VSERVER1.canoga.com> <4D80FAAB.6070407@sbcglobal.net> <4D80FE4F.4040607@oracle.com> <4D810711.6020903@sbcglobal.net> Mail-Followup-To: derby-dev@db.apache.org Date: Wed, 16 Mar 2011 20:42:12 +0100 In-Reply-To: <4D810711.6020903@sbcglobal.net> (Mike Matrigali's message of "Wed, 16 Mar 2011 11:53:05 -0700") Message-ID: User-Agent: Gnus/5.110014 (No Gnus v0.14) Emacs/24.0.50 (usg-unix-v) MIME-Version: 1.0 Content-Type: text/plain X-Source-IP: acsmt357.oracle.com [141.146.40.157] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090207.4D811298.0044,ss=1,fgs=0 Mike Matrigali writes: > My main concern has always been just the background work affecting > existing applications. At this point I have been convinced that default > on is in keeping with the zero admin goal, and that we have a workaround > easily implemented in the field if there are problems. So if we are > going to enable this enventually > I would much rather do it in the first release, rather than a subsequent > point release. I agree that turning it on by default does sound right for a zero-admin db. And since we believe that it won't cause any serious problems in its current state, I'm fine with enabling it. Most users shouldn't even notice that it's there, and those who do can easily disable it, as documented in the release notes. Hopefully they'll also file bug reports about problems they encounter, so that we can improve it further in later releases. But it's getting very close to the RC, and if the release manager thinks it's too risky to reintroduce it at this point, I'm fine with that too. -- Knut Anders