db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3598) Modify ReleaseNoteGenerator and ChangesGenerator to exclude issues that are fixed in earlier releases
Date Wed, 27 May 2009 14:00:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713576#action_12713576
] 

Rick Hillegas commented on DERBY-3598:
--------------------------------------

Hi Myrna,

It sounds like the logic at the end of the constructor for JiraIssue may not be properly parsing
the list of fixed versions in the new xml format for JIRA issues.

> Modify ReleaseNoteGenerator and ChangesGenerator to exclude issues that are fixed in
earlier releases
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3598
>                 URL: https://issues.apache.org/jira/browse/DERBY-3598
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.4.1.3
>            Reporter: Dyre Tjeldvoll
>            Priority: Minor
>         Attachments: derby-3598.diff, derby-3598.v2.diff, derby-3598.v2.stat, DERBY-3598.v3.diff
>
>
> Since we cannot create a Jira filter which selects issues with a set fix versions and
at the same time EXCLUDE issues with another set of fix versions, it would be nice if the
*Generator programs could filter out those issues already fixed in previously released versions.

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