Apache Logo
The Apache Way Contribute ASF Sponsors

Formal board meeting minutes from 2010 through present. Please Note: The board typically approves minutes from one meeting during the next board meeting, so minutes will be published roughly one month later than the scheduled date. Other corporate records are published, as is an alternate categorized view of all board meeting minutes.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

BeanValidation

21 Dec 2011

Bean Validation was accepted into Incubator on 1 March 2010.

The Bean Validation project is an implementation of the Java EE Bean
Validation JSR303 specification.

There are no other important issues open before a possible graduation.
The project has agreed to seek status as a TLP, and has agreed by an internal
vote on its readiness to graduate [1].  The primary task outstanding is the
completion of a charter.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of

* none

How has the community developed since the last report

* Mailing list and JIRA activity are extremely quiet.  We attribute this
to the nature of the podling, being but an implementation of a specification,
and the level of achievement of conformity to that specification.

How has the project developed since the last report

* we have upgraded to and continue to pass the latest available version of
the JSR303 TCK.
* we continue to track the progress of the JSR303 spec for the future.

[1] http://markmail.org/thread/5wrg6zgj7s66dnwg

26 Oct 2011

Bean Validation was accepted into Incubator on 1 March 2010.

The Bean Validation project is an implementation of the Java EE Bean
Validation JSR303 specification.

There are no other important issues open before a possible graduation.
Actually the project is discussing its graduation as TLP or into
Apache Commons, as natural successor of Commons Validator.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of

* none

How has the community developed since the last report

* Users community activity is stable, users slightly decreased the
activity of filling issues on JIRA and asking questions, we suppose
codebase/provided documentation start being mature enough to satisfy
users needs.

How has the project developed since the last report.

* Started a 'extras' module development where putting validators
not included in the JSR303 spec.
* planning the development for implementing next JSR330 spec version.

21 Sep 2011

Bean Validation was accepted into Incubator on 1 March 2010.

The Bean Validation project is an implementation of the Java EE Bean
Validation JSR303 specification.

There are no other important issues open before a possible graduation.
Actually the project is discussing its graduation as TLP or into
Apache Commons, as natural successor of Commons Validator.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of

* none

How has the community developed since the last report

* Users community activity is stable, users slightly decreased the
activity of filling issues on JIRA and asking questions, we suppose
codebase/provided documentation start being mature enough to satisfy
users needs.

How has the project developed since the last report.

* Started a 'extras' module development where putting validators
not included in the JSR303 spec.
* planning the development for implementing next JSR330 spec version.

15 Jun 2011

Apache Bean Validation will deliver an implementation of the JSR303 Bean
Validation 1.0 specification. BVAL entered incubation on March 1, 2010.

A list of the three most important issues to address in the move towards
graduation.
* Perform successful Releases - Done
* Grow the community and committer base - stale at a medium level
* Decide on graduation target of TLP or subproject - TBD

The BVAL community is still discussing about the 3 possible graduation
scenarios:
* Graduate as TLP
* Graduate as part of Apache Commons
* Graduate under the Geronimo TLP

The codebase is mature and stable, thus there is not much development effort
going on atm. Otoh this means that there are not many developers working
actively on BVAL.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of?
. None at this time.

How has the community developed since the last report?
. No new committers.

How has the project developed since the last report?
. 0.3-incubating was released on 2011-02-04.

16 Mar 2011

Failed to report.  There is some degree of activity on its mailing lists,
and addition of new Committers.

19 Jan 2011

The community missed their December quarterly report. So, are submitting
this report in January.

Summary

The community has been active with discussions on the dev list and code
updates. A new 0.3 release has been discussed, but is not yet underway.

Community
 * No new committers...
 * No new PMC members...

Development
 * No new releases, but a 0.3 release has been discussed.
 * Work on annotations for commons-lang 3
 * Many bug fixes

Project Branding

 * Not started yet.

15 Dec 2010

Did not report.

22 Sep 2010

Apache Bean Validation will deliver an implementation of the JSR303 Bean
Validation 1.0 specification. BVAL entered incubation on March 1, 2010.

A list of the three most important issues to address in the move towards
graduation.
* First release of artifacts - Done
* Grow the community and committer base - ongoing
* Decide on graduation target of TLP or subproject - TBD

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of?
* None at this time.

How has the community developed since the last report?
* New committer Matt Benson has started working on a branch to upgrade to
commons-lang v3.

How has the project developed since the last report?
* 0.2-incubating was released on August 20th.

18 Aug 2010

Apache Bean Validation will deliver an implementation of the JSR303 Bean
Validation 1.0 specification. BVAL entered incubation on March 1, 2010.

A list of the three most important issues to address in the move towards
graduation.

 * First release of artifacts - Done
 * Grow the community and committer base - ongoing
 * Decide on graduation target of TLP or subproject - TBD

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of?

 * None at this time.

How has the community developed since the last report?

 * Committer offer was extended and accepted by Matt Benson.
 * A couple of new users on the dev list.

How has the project developed since the last report?

 * Currently a 0.2-incubating RC2 release vote is underway.

21 Jul 2010

Apache Bean Validation will deliver an implementation of the JSR303 Bean
Validation 1.0 specification. BVAL entered incubation on March 1, 2010.

A list of the three most important issues to address in the move towards
graduation.

 * First release of artifacts - Done
 * Grow the community and committer base - ongoing
 * Decide on graduation target of TLP or subproject - TBD

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of?

 * None at this time.

How has the community developed since the last report?

 * PPMC membership was extended and accepted by Carlos Vara.
 * Committer offer was extended and accepted by David Jencks.
 * Growing activity on the dev list for two potential committers.

How has the project developed since the last report?

 * Started discussions about potential content for a 0.2-incubating release.
 * Bean Validation benchmark app contributed by Carlos Vara to help with
performance testing against the Hibernate RI.

16 Jun 2010

Apache Bean Validation will deliver an implementation of the JSR303 Bean
Validation 1.0 specification.  BVAL entered incubation on March 1, 2010.

A list of the most important issues to address in the move towards
graduation
* First release of artifacts.
* Grow the community and committer base.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of
* None at this time.

How has the community developed since the last report
* Committer offer was extended and accepted by Carlos Vara.
* Apache Geronimo has started using our artifacts in their 3.0 builds for
Java EE 6.
* Apache OpenJPA has started creating a image-gallery sample that shows how
JPA2 and our Bean Validation implementation can be used together.

How has the project developed since the last report
* Rsync of Confluence content to our website is now setup.
* Code has been passing the Bean Validation TCK since May 21.
* We completed our first release on June 11, 2010, which was released as
0.1-incubating.

19 May 2010

Apache Bean Validation will deliver an implementation of the JSR303 Bean
Validation 1.0 specification. BVAL entered incubation on March 1, 2010.

A list of the three most important issues to address in the move towards
graduation:

First release of artifacts. Grow the community and committer base.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:

None at this time.

How has the community developed since the last report:

The community has been focused on resolving TCK failures, with lots of help
coming from contributor Carlos Vara. Apache OpenJPA trunk is now using our
artifacts as their default provider for Bean Validation testing. Two other
projects (one at the ASF) have mentioned they are using our artifacts
instead of Hibernate.

How has the project developed since the last report:

Confluence is setup as our website and has been fully populated. SNAPSHOT
artifacts are being published to repository.apache.org. TCK testing is being
run by 3 or 4 committers and contributors.

21 Apr 2010

Bean Validation will deliver an implementation of the JSR303 Bean Validation
1.0 specification.

There are currently no issues requiring IPMC or Board attention.

Since Bean Validation entered incubation on March 1, 2010, we have
accomplished the following:

1. Initial project resources and accounts created
2. Initial code contribution under SGA from Agimatec GmbH imported into svn
3. Source code package names updated from com.agimatec to org.apache.bval
4. Agimatec copyright moved to NOTICE files and removed from source
5. Three committers are already active making code updates
6. Started setup of our Confluence space as our main website
7. Already have one non-committer using the code and submitting patches

Upcoming major goals:

1. Finish setup of website
2. Setup and usage of Nexus
3. First release of artifacts
4. Start TCK testing

Top 2 or 3 things to resolve before graduation:

1. Build community
2. Create at least one release