Below is the quarterly report I submitted to the board. Thanks all,
and let me know if I missed anything.
bryan
## Description:
The mission of the Apache DB project is to create and maintain
commercial-quality, open-source, database solutions based on software licensed
to the Foundation, for distribution at no charge to the public.
The Apache DB TLP consists of the following subprojects:
o Derby : a relational database implemented entirely in Java.
o JDO : focused on building the API and the TCK for compatibility
testing of Java Data Object implementations providing data
persistence.
o Torque : an object-relational mapper for Java.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache DB was founded 2002-07-16 (19 years ago)
There are currently 47 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Georg Kallidis on 2020-08-26.
- No new committers. Last addition was Tobias Bouschen on 2021-01-19.
## Project Activity:
The DB project received a report of a CWE-502 vulnerability in the retired
DdlUtils source code. Although the DdlUtils subproject is retired and no
longer actively developed, the DB project decided to address the
vulnerability, which is now tracked as CVE-2021-41616, and removed the
insecure source code from the source repository. The DB project also removed
the DdlUtils-1.0 release from distribution via the Apache mirrors, and updated
the DdlUtils web site to make it more clear that DdlUtils is retired and no
longer actively developed.
The JDO team have been making changes suggested by the Apache Diversity
Conscious Language Checker, including changing the name of the git branch from
master to main, and resolving all issues in the source code and web site.
https://clc.diversity.apache.org/analysis.html?project=db-jdo.git
https://clc.diversity.apache.org/analysis.html?project=db-jdo-site.git
The JDO project is ready to ask the Java Community Process (JCP) to approve
the latest release, JDO 3.2. We have asked for specific guidance to submit the
release to be voted by the JCP. Once the JCP approves the Maintenance Release,
we will formally make the Apache release via the usual DB PMC process.
The Derby team have validated Derby behavior with Java 17. This involved
significant work to address changes due to JEP411.
## Community Health:
DB community health seemed robust this quarter. Questions were asked and
answered on the mailing lists, and project teams collaborated on releases
and other efforts.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
