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? 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? Regards, Konrad > On 3. Jul 2022, at 15:44, Julian Reschke <[email protected]> wrote: > > Am 01.07.2022 um 09:58 schrieb Konrad Windszus: >> Hi, >> I would like to include https://issues.apache.org/jira/browse/JCR-4799 in >> that release. I hope to have a closer look at the attached patch today. If >> it doesn’t break any tests and adding a new test is too hard I would even >> apply without a test. >> WDYT? >> >> Konrad > > I usually prefer only to put in fixes into stable releases that had an > unstable release before. > > Unless there's an emergency. Is there? In which case I would release > 2.21.* first, and then 2.20.6 sometime later. > > Best regards, Julian
