[
https://issues.apache.org/jira/browse/DERBY-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4857:
-----------------------------------
Attachment: derby-4857-4a-jirasoap_ant_integration.diff
Attached new version of patch 4a due to having used the wrong property name in
the help text.
Rick,
if you run 'ant genrelnotes' you should get all the information you need.
I'll take the patches for a test-spin on Windows, and if that works out okay
I'll just commit them.
> 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.
