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 Thu, 28 Oct 2010 08:12:07 GMT

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

Kristian Waagan commented on DERBY-4857:

Hi Lily,

'ant genrelnotes' will overwrite the existing RELEASE-NOTES.html. You should be able to see
that using 'svn st|diff'. Remember that you still have to edit releaseSummary.xml for the
release notes to be complete and correct.

If you look at the start and end of the fixedBugsList.txt, you should see a few important
pieces of information (this is also printed to standard out when you run the target):
 o the target release version
 o the derived previous release version (this is checked against the one entered in releaseSummary.xml)
 o the derived ancestry chain (used to exclude issues)
 o issue statistics (# total, # written, # disqualified, # release note)

Also included in the output is the path to the output file.

This patch doesn't touch the logic bumping the last digit. I think that is something Rick
is, or have been, working on.
Did you run 'ant genrelnotes' on Windows?

FYI, I expect there will be at least one more patch for this issue, but I'd like to wait for
Rick's further feedback as well.


> 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,
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, 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.

View raw message