bval-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r816786 - in /websites/staging/bval/trunk/content: ./ board-reports/2012-05.html
Date Wed, 09 May 2012 00:20:39 GMT
Author: buildbot
Date: Wed May  9 00:20:39 2012
New Revision: 816786

Staging update by buildbot for bval

    websites/staging/bval/trunk/content/   (props changed)

Propchange: websites/staging/bval/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed May  9 00:20:39 2012
@@ -1 +1 @@

Modified: websites/staging/bval/trunk/content/board-reports/2012-05.html
--- websites/staging/bval/trunk/content/board-reports/2012-05.html (original)
+++ websites/staging/bval/trunk/content/board-reports/2012-05.html Wed May  9 00:20:39 2012
@@ -168,43 +168,28 @@ $content
          <td height="100%">
            <!-- Content -->
-           <div id="BValContent_" class="wiki-content"><h2 id="apache-bval-report-april-2012">Apache
BVal Report April 2012</h2>
+           <div id="BValContent_" class="wiki-content"><h2 id="apache-bval-report-may-2012">Apache
BVal Report May 2012</h2>
 <p>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.</p>
 <h3 id="releases">Releases</h3>
-<p>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.</p>
+<p>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.</p>
 <h3 id="activity">Activity</h3>
-<p>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.</p>
-<p>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.</p>
+<p>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.</p>
+<p>Traffic on the user mailing list remains low/nonexistent.</p>
 <p>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.</p>
 <h3 id="community">Community</h3>
-<p>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
+<p>No new faces in the community.</p>
 <h3 id="branding">Branding</h3>
-<p>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.</p>
+<p>The task of creating a new project logo remains open.</p>
 <h3 id="legal">Legal</h3>
 <p>No concerns at present.</p>
 <h3 id="infrastructure">Infrastructure</h3>
-<p>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.</p></div>
+<p>Nothing needed at the moment.</p></div>
            <!-- Content -->

View raw message