bval-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1644521 - /bval/cms-site/trunk/content/board-reports/2014-12.mdtext
Date Wed, 10 Dec 2014 21:00:03 GMT
Author: mbenson
Date: Wed Dec 10 21:00:03 2014
New Revision: 1644521

CMS commit to bval by mbenson

      - copied, changed from r1644255, bval/cms-site/trunk/content/board-reports/2014-09.mdtext

Copied: bval/cms-site/trunk/content/board-reports/2014-12.mdtext (from r1644255, bval/cms-site/trunk/content/board-reports/2014-09.mdtext)
--- bval/cms-site/trunk/content/board-reports/2014-09.mdtext (original)
+++ bval/cms-site/trunk/content/board-reports/2014-12.mdtext Wed Dec 10 21:00:03 2014
@@ -1,16 +1,23 @@
-## Apache BVal Report September 2014 ##
+## Apache BVal Report December 2014 ##
 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.
 ### Releases ###
-No new releases.
+No new releases. Last release was v0.5 in September 2012.
 ### Activity ###
-Low, but clearly discernible, JIRA/commit activity this quarter. Currently the 
-project has but one active committer. A lack of volunteer availability/energy 
-has left the Commons Weaver dependency situation yet unresolved, but all things in time.
+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.
 ### Community  ###
 No changes in community.

View raw message