Branching for 2.20, was: Jackrabbit 2.19.6 Release Plan

[Julian Reschke <re...@apache.org>]

On 04.12.2019 14:40, Julian Reschke wrote:
> Hi,
> 
> I'd like to cut Jackrabbit 2.19.6 on tomorrow.
> 
> Note that this will likely be the last release before branching for 2.20.
> ...

I'm planning to branch for 2.20 tomorrow. The first release will be 
2.20.0 first week in January; in time for the release of Oak 1.22.0.

Please let me know if there are any concerns.

Best regards, Julian

Re: Branching for 2.20, was: Jackrabbit 2.19.6 Release Plan

[Julian Reschke <re...@apache.org>]

On 17.12.2019 13:59, Julian Reschke wrote:
> On 04.12.2019 14:40, Julian Reschke wrote:
>> Hi,
>>
>> I'd like to cut Jackrabbit 2.19.6 on tomorrow.
>>
>> Note that this will likely be the last release before branching for 2.20.
>> ...
> 
> I'm planning to branch for 2.20 tomorrow. The first release will be 
> 2.20.0 first week in January; in time for the release of Oak 1.22.0.
> 
> Please let me know if there are any concerns.
> 
> Best regards, Julian

In the meantime, I have branched 2.20, and moved the remaining open 
issues targeted for it to 2.22 
<https://issues.apache.org/jira/projects/JCR/versions/12346639>:

> Bug
> 
>     [JCR-3943] - [jackrabbi-aws-ext] Data inconsistency due to race condition during async uploads
>     [JCR-3995] - occasional test failure in AccessControlManagerImplTest.testAddingFourAccessControlEntries()
>     [JCR-4073] - jackrabbit-data: occasional test failures in TestLocalCache.testAutoPurge
> 
> Improvement
> 
>     [JCR-4023] - [S3DS] Configure failure count in initial migration of blobs from file system to S3
> 
> Task
> 
>     [JCR-4076] - no test coverage for JCR-2582
>     [JCR-4219] - Specify versions for maven plugins used in build for ensuring stable builds


Best regards, Julian