Hi, Shouldn’t we first clean up/understand https://issues.apache.org/jira/browse/OAK-11470/OAK-11473?
To quote Robert from https://lists.apache.org/thread/qh3p31gjbmgw4y8v2y1tbfs32lrtrrdw > What I am not that onboard with is respinning a release without a good > understanding about why the initial release was broken to start with. I think > there is no rush to get this release out the door and we should do it with a > good regression test in place. Now almost two months passed and still no insights on the root cause of OAK-11470? For me this is wrong priorities. Reverting based on external ITs not shared with Apache may be ok as short term thing, but definitely not a healthy condition. Konrad > On 2. Apr 2025, at 23:10, Julian Reschke <julian.resc...@gmx.de.INVALID> > wrote: > > A candidate for the Jackrabbit Oak 1.78.0 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.78.0/ > > The release candidate is a zip archive of the sources in: > > https://github.com/apache/jackrabbit-oak/tree/jackrabbit-oak-1.78.0/ > > The SHA1 checksum of the archive is > 6a749c9052e497a4f17448b99a04370aad1382e4. > > A staged Maven repository is available for review at: > > > https://repository.apache.org/content/repositories/orgapachejackrabbit-1703/ > > The command for running automated checks against this release candidate is: > > # run in SVN checkout of > https://dist.apache.org/repos/dist/dev/jackrabbit > $ sh check-release.sh oak 1.78.0 > 6a749c9052e497a4f17448b99a04370aad1382e4 > > Please vote on releasing this package as Apache Jackrabbit Oak 1.78.0. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit Oak 1.78.0 > [ ] -1 Do not release this package because... > > Best regards, Julian
