bval-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r954404 - in /websites/staging/bval/trunk/content: ./ board-reports/2015-06.html
Date Wed, 10 Jun 2015 18:11:37 GMT
Author: buildbot
Date: Wed Jun 10 18:11:37 2015
New Revision: 954404

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 Jun 10 18:11:37 2015
@@ -1 +1 @@

Modified: websites/staging/bval/trunk/content/board-reports/2015-06.html
--- websites/staging/bval/trunk/content/board-reports/2015-06.html (original)
+++ websites/staging/bval/trunk/content/board-reports/2015-06.html Wed Jun 10 18:11:37 2015
@@ -122,19 +122,19 @@ under the License.
   <div class="container" id="BValContent_">
-<h2 id="apache-bval-report-march-2015">Apache BVal Report March 2015</h2>
+<h2 id="apache-bval-report-june-2015">Apache BVal Report June 2015</h2>
 <p>The Apache BVal project implements the Java EE Bean Validation specification(s)
 and related extensions, and became a top-level project of the foundation on
 February 15, 2012.</p>
 <h3 id="releases">Releases</h3>
-<p>No new releases. Last release was v0.5 in September 2012.</p>
+<p>The Apache BVal 1.1.0 release vote passed on June 9, 2015. The formal release
+process continues.</p>
 <h3 id="activity">Activity</h3>
-<p>Our activity level certainly does not mark us as a glamorous project; there has
-been a single commit since the report of Q4 2014. Mailing list traffic is
-nonexistent. Once again, there is little reason to fear we would be unable to
-release from a voting perspective, but our current level of developer "steam" is
-such that a release vote is not a concern for the immediate future. All hope is
-not lost but volunteer burnout is certainly a factor.</p>
+<p>A small flurry of activity has brought the 1.1.0 release to pass. Because Apache
+BVal's semantic version numbers are intended to track the version of the Bean
+Validation specification targeted, this has resulted in the 1.1.0 release
+(implementing Bean Validation 1.1) actually having preceded a 1.0.0 release,
+which remains outstanding.</p>
 <h3 id="community">Community</h3>
 <p>No changes in community.
 Last PMC member added Q4 2013

View raw message