While looking through the changes for this version, I noticed recent commit
r1694984 [1] was incorrectly marked/commented with issue OAK-2231, not a
Jackrabbit JCR issue.
As result these changes are not tracked/reported in the RELEASE-NOTES.txt
either.
It might be good to at least still create a JCR issue for this change, linked to
OAK-2231 and the commit revision [1] for future tracking and release notes
generation.
Kind regards,
Ate
[1] http://svn.apache.org/r1694984
On 2015-08-12 14:23, Davide Giannella wrote:
A candidate for the Jackrabbit 2.11.0 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/2.11.0/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/tags/2.11.0/
The SHA1 checksum of the archive is
c2a2289b391f827dbca5d6ba6e7c532a5046fde6.
A staged Maven repository is available for review at:
https://repository.apache.org/
The command for running automated checks against this release candidate is:
$ sh check-release.sh 2.11.0 c2a2289b391f827dbca5d6ba6e7c532a5046fde6
Please vote on releasing this package as Apache Jackrabbit 2.11.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 2.11.0
[ ] -1 Do not release this package because...
