From dev-return-6925-apmail-stdcxx-dev-archive=stdcxx.apache.org@stdcxx.apache.org Mon Feb 11 17:07:03 2008 Return-Path: Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: (qmail 81325 invoked from network); 11 Feb 2008 17:07:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Feb 2008 17:07:03 -0000 Received: (qmail 89184 invoked by uid 500); 11 Feb 2008 17:06:57 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 89117 invoked by uid 500); 11 Feb 2008 17:06:57 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 89101 invoked by uid 99); 11 Feb 2008 17:06:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2008 09:06:56 -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 [208.30.140.160] (HELO moroha.roguewave.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2008 17:06:26 +0000 Received: from exchmail01.Blue.Roguewave.Com (exchmail01.blue.roguewave.com [10.22.129.22]) by moroha.roguewave.com (8.13.6/8.13.6) with ESMTP id m1BH6VY1002930 for ; Mon, 11 Feb 2008 17:06:32 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [jira] Resolved: (STDCXX-691) Global 'size_t' type in source file 'tests/regress/27.stringbuf.xsputn.stdcxx-515.cpp'. Date: Mon, 11 Feb 2008 10:07:04 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [jira] Resolved: (STDCXX-691) Global 'size_t' type in source file 'tests/regress/27.stringbuf.xsputn.stdcxx-515.cpp'. Thread-Index: AchnmqXniwIB3N6ySViDVwVPO/HQ6wFNNjQg References: <15379715.1201542694807.JavaMail.jira@brutus> <479E173B.4020604@roguewave.com> <47A7C246.9010704@rowe-clan.net> From: "Eric Lemings" To: X-Virus-Checked: Checked by ClamAV on apache.org =20 > -----Original Message----- > From: William A. Rowe, Jr. [mailto:wrowe@rowe-clan.net]=20 > Sent: Monday, February 04, 2008 6:56 PM > To: dev@stdcxx.apache.org > Subject: Re: [jira] Resolved: (STDCXX-691) Global 'size_t'=20 > type in source file=20 > 'tests/regress/27.stringbuf.xsputn.stdcxx-515.cpp'. >=20 > Martin Sebor wrote: > > The issue should be linked as a duplicate of STDCXX-614 and > > on closing the Status set to Duplicate. We might also need > > to edit the time tracking info so we don't throw off our > > reporting (I don't know if it would). >=20 > Keep in mind, although time tracking is interesting data (even as > an open source effort), while you have a community project we need > to recognize it's only a rough approximation. Using this as any > sort of bookkeeping feature for corporate analysis would be abusing > the process. >=20 > So I agree(d) with turning on the feature, understanding what parts > of the code demand the most attention (or possibly also the most > audit-from-behind based on the amount of effort expended in certain > areas of the code). But I'd disagree if this was expected to be > 100% spot-on with the specific time used, and would caution that > this feature is essentially opt-in/voluntary and probably variable > when it comes to multi-day review of a bug. Believe me when I say the time tracking feature within Jira has caused more concern within our particular company, which uses a separate project management tool, than without. I agree with all of your conclusions and everyone should be made aware that use of this feature is purely voluntary and musn't be used for any actual accounting purposes other than personal management practices. Some may use it intensively, others (more likely) not at all. Eric.