svn commit: r1666594 - /bval/cms-site/trunk/content/board-reports/2015-03.mdtext

[mb...@apache.org]

Author: mbenson
Date: Fri Mar 13 22:04:21 2015
New Revision: 1666594

URL: http://svn.apache.org/r1666594
Log:
CMS commit to bval by mbenson

Added:
    bval/cms-site/trunk/content/board-reports/2015-03.mdtext
      - copied, changed from r1655891, bval/cms-site/trunk/content/board-reports/2014-12.mdtext

Copied: bval/cms-site/trunk/content/board-reports/2015-03.mdtext (from r1655891, bval/cms-site/trunk/content/board-reports/2014-12.mdtext)
URL: http://svn.apache.org/viewvc/bval/cms-site/trunk/content/board-reports/2015-03.mdtext?p2=bval/cms-site/trunk/content/board-reports/2015-03.mdtext&p1=bval/cms-site/trunk/content/board-reports/2014-12.mdtext&r1=1655891&r2=1666594&rev=1666594&view=diff
==============================================================================
--- bval/cms-site/trunk/content/board-reports/2014-12.mdtext (original)
+++ bval/cms-site/trunk/content/board-reports/2015-03.mdtext Fri Mar 13 22:04:21 2015
@@ -1,4 +1,4 @@
-## Apache BVal Report December 2014 ##
+## Apache BVal Report March 2015 ##
 
 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
@@ -8,16 +8,12 @@ February 15, 2012.
 No new releases. Last release was v0.5 in September 2012.
 
 ### Activity ###
-The Commons Weaver quasi-dependency bottleneck has as long last been resolved
-and BVal development has resumed. We continue to work with the Apache TomEE PMC,
-who bundle our project and thereby provide a clear barometer for ease of
-integration. I note the question on the agenda of whether we have enough
-committers to make releases... I assume this refers to BVal, though it could
-have referred to Commons as we did spend an unfortunate amount of time blocked
-there. While the developer energy of most of the PMC is being expended 
-elsewhere, I believe we have strong enough representation amongst the wider 
-"ApachEE" (i.e. JEE at Apache) community to be handily able to garner the votes
-for a release once we are satisfied with the state of the codebase.
+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.
 
 ### Community  ###
 No changes in community.