Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <23427707.59831288018999993.JavaMail.jira@thor>
Date: Mon, 25 Oct 2010 11:03:19 -0400 (EDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4857) Utilize the SOAP API to fetch JIRA
 issue list for release notes generation
In-Reply-To: <2044107.8841287582326586.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Hillegas commented on DERBY-4857:
--------------------------------------

Thanks for the additional patches, Kristian. I think that I will wait for you to commit this work before I test-drive it. How do I run this machinery now? I suspect that "ant genrelnotes" isn't good enough. I probably need to specify a number of variables (such as my jira credentials, the release id, the filter id, etc..). What does the command line look like?

I'm happy with a single master target.

Thanks.

> Utilize the SOAP API to fetch JIRA issue list for release notes generation
> --------------------------------------------------------------------------
>
>                 Key: DERBY-4857
>                 URL: https://issues.apache.org/jira/browse/DERBY-4857
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.7.1.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4857-1a-jirasoap_relnotes.diff, derby-4857-1a-jirasoap_relnotes.stat, derby-4857-2a-jirasoap_maven_client.diff, derby-4857-2a-jirasoap_maven_client.stat, derby-4857-3a-jirasoap_relnotesgen_changes.diff, derby-4857-3a-jirasoap_relnotesgen_changes.stat, derby-4857-4a-jirasoap_ant_integration.diff, derby-4857-4a-jirasoap_ant_integration.stat
>
>
> Somewhat simplified, the release manager (RM) must currently perform the following manual steps to feed the release note generate the data it needs:
>  a) Create manual JIRA filter to select issues addressed by the release.
>  b) Save the filter result to disk as XML.
>  c) Write/modify the XML parser to be able to parse the report.
>  d) Determine and record all JIRA release note attachment ids for the issues requiring a release note.
> By using the current version of the SOAP API (3.13.5), steps (b) to (d) can be removed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.