From stdcxx-dev-return-4313-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Tue Aug 14 00:36:48 2007 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 23651 invoked from network); 14 Aug 2007 00:36:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Aug 2007 00:36:48 -0000 Received: (qmail 70970 invoked by uid 500); 14 Aug 2007 00:36:46 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 70955 invoked by uid 500); 14 Aug 2007 00:36:46 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 70943 invoked by uid 99); 14 Aug 2007 00:36:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Aug 2007 17:36:46 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2007 00:36:56 +0000 Received: from qxvcexch01.ad.quovadx.com ([192.168.170.59]) by moroha.quovadx.com (8.13.6/8.13.6) with ESMTP id l7E0aKk7015356 for ; Tue, 14 Aug 2007 00:36:20 GMT Received: from [10.70.3.113] ([10.70.3.113]) by qxvcexch01.ad.quovadx.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Aug 2007 18:35:39 -0600 Message-ID: <46C0F904.7070703@roguewave.com> Date: Mon, 13 Aug 2007 18:36:20 -0600 From: Martin Sebor Organization: Rogue Wave Software, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: stdcxx-dev@incubator.apache.org Subject: Re: Jira issues against trunk References: <46BCA39D.7000807@roguewave.com> <46BCA52C.5050800@roguewave.com> In-Reply-To: <46BCA52C.5050800@roguewave.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Aug 2007 00:35:40.0015 (UTC) FILETIME=[0A2E1FF0:01C7DE0B] X-Virus-Checked: Checked by ClamAV on apache.org I agree. Unless someone has a better idea (hint -- it would be nice to get feedback from others as well :) I'll go with trunk. Martin Andrew Black wrote: > The only benefit I can see in using -dev over trunk, is it > would provide a view into what release the bug was discovered (and > fixed) in. This assistance may be offset by the extra maintenance > hassle of creating the new name every release, and having to deal with > people inadvertently reporting bugs as being part of a previous trunk > version. > > My tendency is to cast a vote for using 'trunk'. > > --Andrew Black > > Martin Sebor wrote: >> It occurs to me that our current process of assigning bugs >> to a yet unreleased branch (e.g., 4.2) might lead to the >> misleading impression after the branch is released that it >> was/is full of bugs even though all the bugs may have been >> resolved before the release went out the door. I think we >> need a separate version entry in Jira for regressions >> introduced during development. Any suggestions for what >> this entry ought to be? Would labeling them simply "trunk" >> work or is there any benefit in being more specific (e.g., >> -dev)? >> >> Martin