Am 03.07.2022 um 20:33 schrieb Konrad Windszus:
Hi,
Technically https://issues.apache.org/jira/browse/JCR-4799 is a regression
introduced by https://issues.apache.org/jira/browse/JCR-4536 (shipped in
2.20.3). Not sure about the urgency, though. The risk is pretty low IMHO.
I am not sure how useful a stable/unstable release cycle is for a product like
JR2 which is mostly in maintenance mode. Do we get a lot of feedback for
unstable releases?
No. But I'd like to keep the ability to have new things such as major
Tika upgrades in unstable releases for some time window.
Wouldn’t it reduce the effort for backporting if we switch to a release model
where we consider every release stable?
How many feature (non-bugfix) additions do we expect, given that Jackrabbit API
is now part of Oak?
The release model of Oak
(https://jackrabbit.apache.org/oak/docs/roadmap.html#release-model) is IMHO
quite successful so should we switch to that for JR2 as well?
In theory yes, in practice I see that:
- seldom releases from trunk/master despite active development, and
- little effort to port things back to 1.22.
So I'm reluctant to agree that this works as well as it was intended.
Regards,
Konrad
Releases are cheap; I currently do ~1 release per month, distributed
over the unstable branch and two stable branches.
If we need something released early, adding a second release in a month
is no problem at all.
Best regards, Julian
