Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 34503 invoked from network); 3 Apr 2008 16:30:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Apr 2008 16:30:13 -0000 Received: (qmail 82170 invoked by uid 500); 3 Apr 2008 16:30:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 82139 invoked by uid 500); 3 Apr 2008 16:30:13 -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 82130 invoked by uid 99); 3 Apr 2008 16:30:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 09:30:13 -0700 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-inf-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 16:29:21 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m33GTfsd008277 for ; Thu, 3 Apr 2008 16:29:41 GMT Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JYR00G01C8LPH00@fe-emea-09.sun.com> (original mail from Dyre.Tjeldvoll@Sun.COM) for derby-dev@db.apache.org; Thu, 03 Apr 2008 17:29:41 +0100 (BST) Received: from khepri32.sun.com ([129.159.112.244]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JYR003HOCGEOF10@fe-emea-09.sun.com> for derby-dev@db.apache.org; Thu, 03 Apr 2008 17:29:04 +0100 (BST) Date: Thu, 03 Apr 2008 18:29:02 +0200 From: Dyre.Tjeldvoll@Sun.COM Subject: Re: Problems with ant genchanges In-reply-to: Sender: Dyre.Tjeldvoll@Sun.COM To: derby-dev@db.apache.org Message-id: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT References: <47F3E6EA.90604@sun.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Myrna van Lunteren writes: > I wanted only those issues that were not already fixed in an already > released version...I think the tool automatically picked the last > released version (in my case, 10.2.2.0), but because of the two > versions off the 10.2 branch, there were a number of issues that had > been backported earlier, and were actually fixed in 10.2.1.6; hence > that release shows up as to be excluded in the ChangesFileGenerator. > > I think you'd want everything that's marked fixed 10.4.0.0, and > 10.4.1.0, except if it's marked also fixed in 10.3.1.4, 10.3.1.5 > (which issues would've gotten included into 10.3.2.1), or 10.3.2.1 > which was also a released version, for those would likely be things > that have gotten backported after the initial release off the 10.3 > branch. Issues that got marked fixed in 10.3.2.2 (in addition to > 10.4.0) would be ok to pick up. I think that's all the versions? > > The ChangesFileGenerator should get modified... > > I hope this makes sense... Yes, I think I see what you mean. The problem is that neither the ReleaseNoteGenerator or the ChangesGenerator will filter out those issues already fixed in an update release (without special patching), and there doesn't seem to be a way to search for 'fixVersion == 10.4.* && !(fixVersion == 10.3.2.1 || fixVersion == 10.3.1.4) in Jira. (You can't negate a field predicate). I guess it would be possible to modify the generators to use table functions and SQL to get the correct set of Jira issues. But for the upcoming release candidate I'm just going to patch this by hand. -- dt