Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 30 May 2011 11:44:48 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1289224134.53247.1306755888062.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <187580346.6046.1299012036924.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5080) Utilize JQL to fetch JIRA issue
 list for release notes generation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041097#comment-13041097 ] 

Kristian Waagan commented on DERBY-5080:
----------------------------------------

Thanks, Rick.

Committed patch 2a to trunk with revision 1129117.

I did generate the 10.8 release notes and compared them to what is checked in on the 10.8 branch. Besides from some unrelated formatting differences, the tool now adds a few additional issues because their JIRA status changed (i.e. marked as resolved after the 10.8 release notes were generated), and there was one issue that didn't make it (I assume the issue for the istat feature, DERBY-3788, was added manually?).

I hope I have addressed the issue where there are several release candidates, and I have also made the tool exclude higher versions with the same fix-pack as the release (that is, don't include 10.8.1.3 when generating release notes for 10.8.1.2).

Running the tool with release version 10.8.1.3 results in the delta between 10.8.1.3 and 10.8.1.2 (19 issues at time of writing). This requires that you change the value of previousRelease in releaseSummary.xml.

> Utilize JQL to fetch JIRA issue list for release notes generation
> -----------------------------------------------------------------
>
>                 Key: DERBY-5080
>                 URL: https://issues.apache.org/jira/browse/DERBY-5080
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.8.1.2
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-5080-2a-utilize_jql.diff, derby-5080-2a-utilize_jql.stat
>
>
> DERBY-4857 made it possible to use the JIRA SOAP API to fetch a list of issues fixed in a release. However, the release manager have to manually create a JIRA filter and feed the filter id to the tool.
> Now that the Apache JIRA instance has been updated to 4.x, we can use the JIRA Query Language (JQL) to avoid that manual step.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira