Manfred,

The announcement is posted on the website, but the release notes still say "Bug". Could you make this change to "Bug Fixed"? :)

Thanks,

Jeff Bischoff
Kenneth L Kurz & Associates, Inc.

Manfred Geiler wrote:
That's what JIRA automatically generates.
But I see your point. Will change "Bug" to "Fixed".
Thanks.
--Manfred

On 2/14/07, Barbalace, Richard <[EMAIL PROTECTED]> wrote:
Hi.

Looking at the release notes, I see:
Release Notes - MyFaces Core - Version 1.1.5
 ** Bug
    * [long listing of bugs]

This phrasing is ambiguous. Are these bugs present in the Release, or bugs fixed in the Release? This might be obvious to developers, but release notes should be more friendly to end users who might otherwise be frightened away.

Richard J. Barbalace



> -----Original Message-----
> From: Manfred Geiler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 14, 2007 7:29 AM
> To: MyFaces Development
> Subject: [VOTE] MyFaces Core 1.1.5
>
>
> Hi all,
> This is the official vote for MyFaces Core 1.1.5.
>
> Please note that this vote concerns all of the following parts:
>  1. Maven artifact group "org.apache.myfaces.maven" v1.0.5  [1]
>  2. Maven artifact group "org.apache.myfaces.shared" v2.0.5  [1]
>  3. Maven artifact group "org.apache.myfaces.core" v1.1.5  [1]
>  4. MyFaces Core Assembly  [2]
>  5. Proposed Release Announcement  [3]
>
> [1] http://people.apache.org/builds/myfaces/m2-staging-repository/
> [2] http://people.apache.org/builds/myfaces/core-1.1.5/
> [3] http://wiki.apache.org/myfaces/CoreRelease115#releasenotes
>
> --Manfred
>





The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.







Reply via email to