You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Julian Reschke <ju...@gmx.de> on 2022/07/01 07:56:02 UTC

Jackrabbit 2.20.6 Release Plan

Hi,

I'm planning to cut Jackrabbit 2.20.6 on Monday.

The list of open issues scheduled for 2.20.6 is empty:

https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.20.6%20AND%20project%20%3D%20JCR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC

The CI tests are passing:

https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/

The candidate release notes are here:

https://svn.apache.org/repos/asf/jackrabbit/branches/2.20/RELEASE-NOTES.txt

If there are any objections please let me know.

Best regards, Julian

Re: Jackrabbit 2.20.6 Release Plan

Posted by Julian Reschke <ju...@gmx.de>.
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


Re: Jackrabbit 2.20.6 Release Plan

Posted by Konrad Windszus <kw...@apache.org>.
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 <ju...@gmx.de> 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


Re: Jackrabbit 2.20.6 Release Plan

Posted by Julian Reschke <ju...@gmx.de>.
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

Re: Jackrabbit 2.20.6 Release Plan

Posted by Konrad Windszus <ko...@gmx.de>.
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


> On 1. Jul 2022, at 09:56, Julian Reschke <ju...@gmx.de> wrote:
> 
> Hi,
> 
> I'm planning to cut Jackrabbit 2.20.6 on Monday.
> 
> The list of open issues scheduled for 2.20.6 is empty:
> 
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.20.6%20AND%20project%20%3D%20JCR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
> 
> The CI tests are passing:
> 
> https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/
> 
> The candidate release notes are here:
> 
> https://svn.apache.org/repos/asf/jackrabbit/branches/2.20/RELEASE-NOTES.txt
> 
> If there are any objections please let me know.
> 
> Best regards, Julian