Hi Groovy (including Geb) & Grails folks,

Any updates/comments before I submit our latest board report?
(Due in two days.)

Thanks, Paul.

===============>8==============

## Description:
Apache Groovy is responsible for the evolution and maintenance of the Groovy
programming language and related projects from the Groovy ecosystem

## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: No issues requiring board attention at this time.

## Membership Data:

Apache Groovy was founded 2015-11-18 (9 years ago)
There are currently 23 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
No new PMC members. Last addition was Soeren Glasius on 2024-11-06.
No new committers. Last addition was Sergio del Amo on 2024-12-20.

## Project Activity:

Recent releases:
4.0.26 was released on 2025-02-28.
3.0.24 was released on 2025-02-27.
4.0.25 was released on 2025-01-25.

The Groovy PMC voted to accept Geb (previously gebish.org) as a Groovy
subproject late last year. There is a draft website and snapshots are currently
available. A first release under the ASF is expected in the next few weeks.

The Groovy PMC voted earlier in the year to sponsor incubation of the Grails
project (grails.org) to become a new TLP when ready. The Grails PPMC is
working well.
* the major Grails repos are now under the ASF organization
* they have voted in new committers and PPMC members
* extensive work has taken place to prepare for a first release
  (including consolidation, licensing and reproducibility for the
  couple of hundred artifacts that are part of a Grails release)

The other major goal of the Groovy PMC over the next quarter is
to move Groovy 5 towards a GA release.

## Community Health:
Overall, community activity has increased this quarter.
Work on incorporating Geb as a subproject is well advanced.
Work helping Grails on their incubation journey is well advanced.
The main Groovy project is preparing its first non-alpha release
of Groovy 5 which is expected shortly.

Reply via email to