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 12:57:23 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-3a-jirasoap_relnotesgen_changes.diff

Attaching patch 3a, which modifies the existing release notes generator classes to work with
the data produced by the JIRA SOAP client.

M       java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java

Changed comments, removed use of ReportParser, adjusted code to use the new code to obtain
the list of JiraIssues.
Removed sanity check from patch 1a (blocked progress).

M       java/build/org/apache/derbyBuild/GeneratorBase.java

Removed use of TagReader.

D       java/build/org/apache/derbyBuild/ReportParser.java

Deleted class (no longer used).

M       java/build/org/apache/derbyBuild/JiraIssue.java

Added code to parse the data file generated by the JIRA SOAP client.
Added method hasMissingReleaseNotes.
Modified constructor.

Patch ready for review. Already tested by Rick, so I expect to commit this shortly.

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