Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Message-ID: <19407509.1155290534357.JavaMail.jira@brutus>
Date: Fri, 11 Aug 2006 03:02:14 -0700 (PDT)
From: "Cyriaque Dupoirieux (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Closed: (FOR-919) Release Notes do not use keys to retrieve
 important changes
In-Reply-To: <4586280.1155287235159.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/FOR-919?page=all ]

Cyriaque Dupoirieux closed FOR-919.
-----------------------------------

    Resolution: Fixed

The release notes actions are retrieved with a key filtering on the @importance.
The let you define your own contexts and see them in the release notes !

> Release Notes do not use keys to retrieve important changes
> -----------------------------------------------------------
>
>                 Key: FOR-919
>                 URL: http://issues.apache.org/jira/browse/FOR-919
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Plugin: input.projectInfo
>    Affects Versions: 0.8-dev
>            Reporter: Cyriaque Dupoirieux
>         Assigned To: Cyriaque Dupoirieux
>            Priority: Trivial
>             Fix For: 0.8-dev
>
>
> Not a real problem, but the changes page is more intelligent, because it is not limited to the following contexts 'code', 'docs',...
> One can define his own contexts with the corresponding tags and these actions won't be take into account in the release note.
> Too bad.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira