Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 64166 invoked from network); 8 Sep 2006 18:23:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Sep 2006 18:23:23 -0000 Received: (qmail 89141 invoked by uid 500); 8 Sep 2006 18:23:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 89111 invoked by uid 500); 8 Sep 2006 18:23:22 -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 89102 invoked by uid 99); 8 Sep 2006 18:23:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2006 11:23:22 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.142] (HELO e2.ny.us.ibm.com) (32.97.182.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2006 11:23:22 -0700 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.13.8/8.12.11) with ESMTP id k88IMvY4004547 for ; Fri, 8 Sep 2006 14:22:57 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k88IMvBl232974 for ; Fri, 8 Sep 2006 14:22:57 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k88IMvr2010782 for ; Fri, 8 Sep 2006 14:22:57 -0400 Received: from [9.48.61.191] (sig-9-48-61-191.mts.ibm.com [9.48.61.191]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k88IMvAB010704 for ; Fri, 8 Sep 2006 14:22:57 -0400 Message-ID: <4501B4FC.604@sbcglobal.net> Date: Fri, 08 Sep 2006 11:22:52 -0700 From: Kathey Marsden Reply-To: kmarsdenderby@sbcglobal.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Release Notes References: <44EB4F17.3090401@sun.com> <54ac72d70608221208i54a247cegad1034a827a91804@mail.gmail.com> <44EDC8B3.8090708@apache.org> <54ac72d70609080123p46be5f88yc5ab6b5ef73387d2@mail.gmail.com> <45017EAA.2080000@sun.com> <4501AC5F.7000301@sbcglobal.net> <4501B322.7080601@apache.org> In-Reply-To: <4501B322.7080601@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Daniel John Debrunner wrote: >Kathey Marsden wrote: > > > >>I hope I am not hijacking this thread but I have a question about the >>release notes. >>The practice of marking multiple fix versions in Jira means that the >>Jira release notes for 10.2 also include all of issues that are fixed >>in 10.2 and previous releases. For example if an issue was marked fixed >>in 10.1.3.1 and 10.2 it shows up in the 10.2 release notes, but really >>should not. >> >> > >I assuming the issues you are refering to were fixed in the trunk after >the 10.1 branch creation and were also fixed in the 10.1 branch. > >Can you explain why they should not show up in the 10.2 release notes? I >guess that assumption confuses me. > > > I was assuming that what is in the release notes is everything that has been fixed since the last release, in our case case since since 10.1.3.1. You think it should be everything since the 10.1 branch originally branched? That doesn't seem that helpful to me as that is not even on a release boundary, but does seem to match our current process. Kathey