[
https://issues.apache.org/jira/browse/DERBY-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan closed DERBY-4857.
----------------------------------
Closing issue.
I have decided to not backport, because there has been a lot of other changes
in the build/release system. This fix isn't dependent on those other fixes, but
to me it makes sense to have a clear cut between where we use new functionality
and where we use old mechanisms. This affects documentation too (mostly wiki).
The release manager(s) should be aware that several release process tasks have
changed in 10.7.
> 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.1
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.7.1.1
>
> 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-3b-jirasoap_relnotesgen_changes.diff,
> derby-4857-4a-jirasoap_ant_integration.diff,
> derby-4857-4a-jirasoap_ant_integration.stat,
> derby-4857-4b-jirasoap_ant_integration.diff, derby-4857-5a-minor_tweaks.diff,
> derby-4857-6a-client_tweaks.diff, RELEASE-NOTES.html
>
>
> 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.
