Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <76270523.1244485807361.JavaMail.jira@brutus>
Date: Mon, 8 Jun 2009 11:30:07 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3598) Modify ReleaseNoteGenerator and
 ChangesGenerator to exclude issues that are fixed in earlier releases
In-Reply-To: <1739710819.1207494924497.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Thanks for tackling this issue, Myrna. I am unable to comment on the code changes. The edits are largely stylistic and refactoring changes, which obscure the functional improvements. If there is a particular functional change or design decision which you'd like to draw my attention to, please let me know. Thanks.

> 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, DERBY-3598.v4.diff, RELEASE-NOTES.html
>
>
> 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.