db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4857) Utilize the SOAP API to fetch JIRA issue list for release notes generation
Date Wed, 20 Oct 2010 20:44:23 GMT

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

Kristian Waagan commented on DERBY-4857:

Hi Rick,

Thanks for trying to test the patch. I'm unable to give you proper feedback right now, but
here are a few quick hints.

The broken build problem will be fixed by DERBY-4858, alternatively you can just revert the
ReportParser class in java/build/org/apache/derbyBuild. I missed this problem because I was
just messing around in tools/release and didn't do a 'ant clobber all' from the root.

You have to go into tools/release/jirasoap and issue the mvn-command from there. The directory
jirasoap contains a fully independent Maven-project. It doesn't depend on the rest of the
Derby code at all.

It is not clear to me that the getAncestors-method is behaving incorrectly, but that may be
the case. Are you able to test this by using a set of the existing releases, or have we not
yet created a scenario as you described with potential future versions in your comment?
For instance, I was under the impression that the current version of the tool is able to deal
correctly with the release. It was released between and The tool
uses the release version and the release date to determine the preceding release.
You can invoke the tool with the ancestors-argument to print the list of ancestors for a given
version (see the usage msg). 


> 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:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4857-1a-jirasoap_relnotes.diff, derby-4857-1a-jirasoap_relnotes.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.

View raw message