Why should retired branches be deleted ?
Shouldn't they instead be somehow put in read-only state but kept
available for anyone needing them ?
My 2 cents,
Cédric
Le 09/01/2024 à 14:40, Christofer Dutz a écrit :
So, I guess the deletion of the “retired” branches should probably be
done by a
Apache Cocoon 2.1 and 3.0 retired
-
After the recent release of Cocoon 2.3.0, the Apache Cocoon Community has
decided to retire both 2.1 and 3.0 versions, to focus on further
developments
of the 2.3 branch
The 2.1 branch was first released
