Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 35334 invoked from network); 5 May 2006 13:33:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 May 2006 13:33:13 -0000 Received: (qmail 94075 invoked by uid 500); 5 May 2006 13:33:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 94029 invoked by uid 500); 5 May 2006 13:33:12 -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 94020 invoked by uid 99); 5 May 2006 13:33:12 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 06:33:12 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.1.36] (HELO gmpea-pix-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 06:33:10 -0700 Received: from d1-emea-05.sun.com ([192.18.2.115]) by gmpea-pix-1.sun.com (8.12.9/8.12.9) with ESMTP id k45DWkOO022251 for ; Fri, 5 May 2006 14:32:48 +0100 (BST) Received: from conversion-daemon.d1-emea-05.sun.com by d1-emea-05.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0IYS00A01MD1W600@d1-emea-05.sun.com> (original mail from Vemund.Ostgaard@Sun.COM) for derby-dev@db.apache.org; Fri, 05 May 2006 14:32:46 +0100 (BST) Received: from [129.159.112.244] by d1-emea-05.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0IYS009XSOALB940@d1-emea-05.sun.com> for derby-dev@db.apache.org; Fri, 05 May 2006 14:32:46 +0100 (BST) Date: Fri, 05 May 2006 15:32:45 +0200 From: Vemund Ostgaard Subject: Re: Derby metrics In-reply-to: <445A33AB.2050300@sbcglobal.net> Sender: Vemund.Ostgaard@Sun.COM To: derby-dev@db.apache.org Message-id: <445B53FD.3080905@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <445A33AB.2050300@sbcglobal.net> User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7.12) Gecko/20050927 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Kathey Marsden [W.P.A YELLOW PAGES] wrote: > I was thinking about Derby Metrics. I think this is a good initiative Kathey, having metrics like these in place would be useful when discussing releases and quality. > 1) Has anyone compiled any of the following information already? > 2) Can you think of additonal metrics that might be useful to the > community? The size of jar-files might be useful to measure/monitor (when compiled with the right flags and options that are used for releases). The intent would be to have awareness on the small, light-weight image. In addition to measuring lines of code added or total, I've also heard about measuring the number of lines of code that have been changed (added/removed/updated), loosely refered to as measuring "code turmoil". With a lot of code turmoil you expect less stability, this number should go down when you get close to a release. > > Derby lines of code by component. > Derby code coverage numbers by component. > Lines of code added for 10.2 by component. > Derby bugs by component and severity. > Derby bug inflow by component and overall. Did you plan to do this as a one shot exercise or did you want to do it periodically, like daily or weekly? I think weekly numbers would be good, would be often enough and might mask uninteresting fluctuations that you might see if producing daily numbers. Vemund