yes, fixed version in jira is not binding. it is a wish :-) I removed them from the 3.1.40 version.
regards, toby On Thu, Jun 22, 2017 at 5:35 PM, Konrad Windszus <[email protected]> wrote: > According to JIRA there are still three outstanding issues for 3.1.40: > https://issues.apache.org/jira/projects/JCRVLT/versions/12339160. Do you want > to move those to the next release? > Konrad > >> On 22. Jun 2017, at 04:14, Tobias Bocanegra <[email protected]> wrote: >> >> Hi, >> >> A candidate for the Jackrabbit Filevault 3.1.40 release is available at: >> >> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.1.40/ >> >> 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.40/ >> >> The SHA1 checksum of the archive is 9ce3ed280c2bb42b1823f9fc7f6ff0e2168ea166. >> >> A staged Maven repository is available for review at: >> >> https://repository.apache.org/content/repositories/orgapachejackrabbit-1256/ >> >> Please vote on releasing this package as Apache Jackrabbit Filevault 3.1.40. >> 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.40 >> [ ] -1 Do not release this package because... >
