bval-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1311921 - /bval/cms-site/trunk/content/board-reports/2012-04.mdtext
Date Tue, 10 Apr 2012 18:52:04 GMT
Author: mbenson
Date: Tue Apr 10 18:52:03 2012
New Revision: 1311921

CMS commit to bval by mbenson

      - copied, changed from r1310645, bval/cms-site/trunk/content/board-reports/2012-03.mdtext

Copied: bval/cms-site/trunk/content/board-reports/2012-04.mdtext (from r1310645, bval/cms-site/trunk/content/board-reports/2012-03.mdtext)
--- bval/cms-site/trunk/content/board-reports/2012-03.mdtext (original)
+++ bval/cms-site/trunk/content/board-reports/2012-04.mdtext Tue Apr 10 18:52:03 2012
@@ -1,29 +1,31 @@
-## Apache BVal Report March 2012 ##
+## Apache BVal Report April 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 actively
-discussing making its first non-incubating release in the *immediate* (!) future.
-We are highly motivated because as members of the Java EE ecosystem @ Apache
-we like to cooperate and coordinate with the release schedules of related
-projects e.g. OpenJPA, Geronimo) whenever possible.
+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.
 ### Activity ###
-Since graduating to TLP status, activity has focused on post-graduation tasks,
-primarily the migration of the BVal website from Confluence to the Apache CMS.
+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.
 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.
-Finally, we have established a #bval channel on Freenode IRC.  We continue to
-make decisions on-list, but we hope that our availability on IRC will help build
-a sense of team camaraderie, and allow us to resolve simple questions in a more
-synchronous manner.
 ### 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
@@ -31,9 +33,9 @@ and we are satisfied that no entity has 
 ### Branding ###
-Most of the team (and everyone else who has been asked) harbor some level of
-dislike for BVal's existing logo, the "check mark made of coffee beans."  One of
-our ongoing tasks is the direction/selection/creation of a new project logo.
+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.
 ### Legal ###
 No concerns at present.

View raw message