Hi Jeffery,

I'm super impressed with your first report.

Thanks,
Craig


> On Apr 7, 2026, at 09:06, Jeffery Painter <[email protected]> wrote:
> 
> Hello,
> 
> Here is the report I have submitted to the board for this quarter.
> Please let me know of any issues or omissions.
> 
> Thank you,
> Jeffery Painter
> 
> 
> ## 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 sub-projects:
>  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.
> 
> 
> ## Project Status:
> Current project status: ongoing
> Issues for the board: none
> 
> Please see the Project Activity section of our report for recent updates.
> 
> ## Membership Data:
> Apache DB was founded 2002-07-16 (24 years ago)
> There are currently 48 committers and 46 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 Max Philipp Wriedt on 2024-07-03.
> - No new committers. Last addition was Max Philipp Wriedt on 2023-04-15.
> 
> ## Project Activity:
> 
> ### Apache JDO
> 
> The JDO project remains active and responsive, with ongoing engagement on
> mailing lists and issue tracking.
> 
> Recent efforts have focused on:
> 
>  - Continued improvements to the codebase driven by SonarCloud analysis,
>    including addressing code quality issues and reducing technical debt.
>  - Ongoing updates to build and CI infrastructure to align with current Maven
>    and Apache POM standards.
>  - Progress toward a future release, pending completion of minor code
>    improvements.
> 
> Additional technical discussions and work include:
> 
>  - Investigation into raising the minimum supported Java version (JDO-812).
>  - Work toward generating SBOM files (JDO-847).
>  - Continued refinement of code quality issues identified in SonarCloud, with
>    active pull requests and incremental progress.
> 
> The project has also encountered some issues with the Trusted Release process,
> particularly related to signing artifacts and build failures in release
> profiles, and is working with the appropriate ASF teams to resolve these.
> 
> ### Apache Torque
> 
> Activity in the Torque project this quarter has been relatively light,
> consisting primarily of minor bug fixes and maintenance.
> 
> The community has begun discussing several potential future directions,
> including:
> 
>  - Planning for a potential major release.
>  - Evaluating database support strategy, including possibly focusing on
>    MySQL/MariaDB based on community usage.
>  - Considering an upgrade to newer Java versions (Java 21 or later).
>  - Reassessing a potential migration from Subversion to Git, though this
>    remains under discussion due to the associated effort.
>  - Continued improvements to the Maven build system and project documentation.
> 
> Security posture was reviewed in light of recent ASF guidance, and no issues
> were identified.
> 
> ### Project-Level Updates
> 
>  - The Apache DB project has completed the PMC Chair transition, with Jeffery
>    Painter now serving as PMC Chair. All onboarding steps have been completed
>    in accordance with ASF guidelines.
> 
> ## Community Health:
> 
> The Apache DB project remains stable and in good health.
> 
> The JDO subproject continues to demonstrate steady development activity, with
> regular attention to code quality, infrastructure updates, and release
> planning. The Torque subproject, while quieter this quarter, maintains a
> stable codebase and ongoing community discussion about its future direction.
> 
> PMC engagement remains solid, with active participation in project discussions
> and decision-making. There are no current concerns requiring board attention.
> 

Craig L Russell
[email protected]

Reply via email to