On 29.01.2020 15:03, Julian Reschke wrote:
...
The concrete steps would be:

- create the branch based on the tag 1.22.0
- flip the default for lazy loading of Lucene index files
- backport selected changes from trunk (such as related to yesterday's CVE)
- release 1.22.1
- (later on) retire 1.10.*
...

Hi there,

in the meantime, all of this was done except the last step. In our
downstream project, we have now successfully replaced Oak 1.10.8 with
Oak 1.22.2, so I believe we can retire the 1.10 branch, recommending
people to use 1.22 instead.

I'm planning to do this at the end of the week; please let me know if
that would cause any problems.

Best regards, Julian

Reply via email to