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] Updated: (DERBY-4857) Utilize the SOAP API to fetch JIRA issue list for release notes generation
Date Mon, 25 Oct 2010 13:49:19 GMT

     [ 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
                derby-4857-4a-jirasoap_ant_integration.stat

Attaching patch 4a, which integrates the JIRA SOAP client with ant.

Hopefully, running 'ant genrelnotes' from tools/release should be enough to get people going.
I won't say more, and will wait for feedback :)

Note that you have to apply both patch 3a and 4a to test this.
For now I have created one master target (I reused genrelnotes), but it may be better to split
it up into two sub-targets to allow for modification of the issue list before running the
release notes generator.
What do those who have been RMs say about that?

Patch ready for review.

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


Mime
View raw message