Mailing-List: contact commits-help@bval.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bval-dev@bval.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1335853 -
 /bval/cms-site/trunk/content/board-reports/2012-05.mdtext
Date: Wed, 09 May 2012 00:20:33 -0000
To: commits@bval.apache.org
From: mbenson@apache.org
Message-Id: <20120509002033.3F64C238896F@eris.apache.org>

Author: mbenson
Date: Wed May  9 00:20:32 2012
New Revision: 1335853

URL: http://svn.apache.org/viewvc?rev=1335853&view=rev
Log:
CMS commit to bval by mbenson

Modified:
    bval/cms-site/trunk/content/board-reports/2012-05.mdtext

Modified: bval/cms-site/trunk/content/board-reports/2012-05.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/trunk/content/board-reports/2012-05.mdtext?rev=1335853&r1=1335852&r2=1335853&view=diff
==============================================================================
--- bval/cms-site/trunk/content/board-reports/2012-05.mdtext (original)
+++ bval/cms-site/trunk/content/board-reports/2012-05.mdtext Wed May  9 00:20:32 2012
@@ -1,46 +1,31 @@
-## Apache BVal Report April 2012 ##
+## Apache BVal Report May 2012 ##
 
 The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303)
 specification and related extensions, and became a top-level project of the
 foundation on February 15, 2012.
 
 ### Releases ###
-BVal version 0.3-incubating was released April 28, 2011.  The PMC is currently
-voting to release BVal 0.4 RC1, which will be integrated into OpenEJB's imminent
-TomEE release.
+BVal proudly made its first non-incubating release, version 0.4, on April 14,
+2012. Ours was incorporated into the better-publicized Apache TomEE 1.0 release.
 
 ### Activity ###
-Recent activity has focused on the 0.4 release, with an eye to the project's
-long-term goals (e.g. minimizing dependencies).  Our next goals are to
-continue improving the codebase so that we can make, as soon as possible,
-a 1.0 release with the best possible interface with which to provide reliability
-to our user base.  Discussions in this regard have already begun.
-
-Traffic on the user mailing list remains low/nonexistent.  As always, we
-consider that to be merely in the nature of providing an implementation of a
-wider-known specification:  the reference implementation gets the user traffic.
+Since the release of BVal 0.4, there has been no activity to speak of. Our next
+goals are to continue improving the codebase for BVal 1.0.
+
+Traffic on the user mailing list remains low/nonexistent.
 
 We continue to follow the progress of the Bean Validation specification; its
 1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349.
-Certain of the features of specification version 1.1.0 duplicate custom
-functionality already implemented in BVal; these must of course be merged.
 Apache BVal will implement Bean Validation v1.1.0 as soon as is practical.
 
 ### Community  ###
-The composition of the team has not changed since graduation, at which time
-all committers became members of the inaugural PMC.  The PMC is quite diverse
-and we are satisfied that no entity has undue influence in our decision-making
-process.
+No new faces in the community.
 
 ### Branding ###
-The task of creating a new project logo remains open, though some positive
-discussion has taken place and seems to be heading in the direction of
-satisfying interested parties.
+The task of creating a new project logo remains open.
 
 ### Legal ###
 No concerns at present.
 
 ### Infrastructure ###
-We have some outstanding features we'd like to implement on our project
-website (specifically a news or blog feed), and may seek advice and/or support
-from infrastructure to accomplish this.
\ No newline at end of file
+Nothing needed at the moment.