db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4857) Utilize the SOAP API to fetch JIRA issue list for release notes generation
Date Sat, 23 Oct 2010 00:25:19 GMT

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

Dag H. Wanvik commented on DERBY-4857:

Discussed Rick's 5) points to define ancestry with Kristian a bit. I think Rick's definition
makes sense: B.y+ is neither an ancestor or descendant of A.x+, so any release notes for patch
P added in A.x+ should not be culled from B.y+. 
Iff A.x is the first release of A, both B.y and B.y+ are descendants of A.x, if I understand
the definition correctly, so fixes made in A.x *should* be culled for B.y as well as for B.y+.

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