Hi Although the build was finally successfu it took 1 hour 24 minutes on my computer and emitted 31 MB of build log. I consider this a state we should definitely revisit.
I am not in favour of releasing the code base in this state. However, I am not blocking this release but I would appreciate at least a revisit of check style and the longest running ITs to achieve - a build log with a decent size - a build not taking longer than 45 minutes Thanks, Konrad > On 12. Jan 2025, at 22:55, Julian Reschke <[email protected]> wrote: > > A candidate for the Jackrabbit Oak 1.74.0 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.74.0/ > > The release candidate is a zip archive of the sources in: > > https://github.com/apache/jackrabbit-oak/tree/jackrabbit-oak-1.74.0/ > > The SHA1 checksum of the archive is cbdc8448ac8cb5f402ef498ced872f49877f2d0b. > > A staged Maven repository is available for review at: > > https://repository.apache.org/ > > 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.74.0 cbdc8448ac8cb5f402ef498ced872f49877f2d0b > > Please vote on releasing this package as Apache Jackrabbit Oak 1.74.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.74.0 > [ ] -1 Do not release this package because... > > Best regards, Julian
