Hi,
Last thread to discuss about Cocon 2.1.x branch, with 2.1.13 released 3
years ago.
Cocoon 2.1 has no dependencies to Maven/Spring and rely on the old
Avalon stuff instead.
Its build system is way outdated, there's no dependency management and
many blocks rely on obsolete/unmaintained 3rd party libs, but its core
is still reliable.
Unfortunately, there's no easy way to migrate from Cocoon 2.1 to 2.2,
that's why this branch still exists.
We'd like to know whether you'd prefer:
[ ] retiring Cocoon 2.1.x
[ ] reviving/maintaining Cocoon 2.1.x, meaning that you volunteer to be
somehow involved
Please note that the above proposal is not a formal vote, but more like
a open poll, so that everyone could speak out.
Cédric
Le 30/11/2023 à 19:53, Cédric Damioli a écrit :
Dear Cocoon users and developers,
Sorry for crossposting here, I wanted to be sure that all involved
people were aware of the ongoing discussions.
We recently pushed a new release of Cocoon, 11 years after the
previous one. This release gathers all changes made in between as well
as two security fixes discovered last year.
The journey to roll this release out was definitively not an easy one,
and it's now time to think about what should be next for the project.
We currently officially maintain 3 branches, not compatible with each
others and having evolved differently over the years : 2.1.x, 2.2/2.3
and 3.0, and we do not have enough active developers to be able to
continue to properly and correctly maintain them.
For a project as old as Cocoon (21 years!), there may be many users
around here still using one branch or another, which could be
interested to step up, contribute and try to revive the project, or at
least some parts of it.
I will soon start 3 threads on the developers list to decide what to
do about each of the 3 branches (retiring or not), so I encourage
volunteers to bring their voices.
Best regards,
Cédric, on behalf of the Apache Cocoon PMC
--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org
