Hi Konrad, no error. We skipped the 3.1.32 version due to an internal versioning hickup. it's written in the release notes:
https://github.com/apache/jackrabbit-filevault/blob/trunk/RELEASE-NOTES.txt#L38-L41 I'll fix the version in JIRA soon. regards, toby On Mon, Jan 16, 2017 at 5:35 PM, Konrad Windszus <[email protected]> wrote: > In JIRA there is only 3.1.32: > https://issues.apache.org/jira/browse/JCRVLT/fixforversion/12338308/ > Is that a typo in the announcement mail? > Konrad > >> On 16 Jan 2017, at 08:36, Tobias Bocanegra <[email protected]> wrote: >> >> A candidate for the Jackrabbit Filevault 3.1.34 release is available at: >> >> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.1.34/ >> >> The release candidate is a zip archive of the sources in: >> >> https://svn.apache.org/repos/asf/jackrabbit/commons/filevault/tags/jackrabbit-filevault-3.1.34/ >> >> The SHA1 checksum of the archive is 4314f86223e8236c3931f831bc7da4d9162dac4c. >> >> A staged Maven repository is available for review at: >> >> https://repository.apache.org/content/repositories/orgapachejackrabbit-1222 >> >> Please vote on releasing this package as Apache Jackrabbit Filevault 3.1.34. >> 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 Filevault 3.1.34 >> [ ] -1 Do not release this package because... >
