Dear all, I just staged JDO 3.2 RC4. Please have a look and report any problems: https://repository.apache.org/content/repositories/orgapachejdo-1004/
Changes: - the "source-release" archives are now signed with SHA512 in addition to md5/sha1 - ReleaseHowTo.md updated Note: In this release all files are still delivered with a .sha1 and .md5 file. This is due to a technical problem which is tracked here: https://issues.apache.org/jira/browse/INFRA-22540 This is also the reason why RC3 failed and was no put up for a vote. Best, Tilmann On 08/11/2021 23:20, Tilmann Zäschke wrote:
Dear all, I just staged JDO 3.2 RC2. Please have a look and report any problems: https://repository.apache.org/content/repositories/orgapachejdo-1002 Changes: - archives are now available as .zip and as .tar.gz - the "source-release" archives are now signed with SHA512 - The pom now has the "timestamp" property - Some updates on the release instructions Note: - The API is still signed with sha1 only. I believe this is in line with the requirement of Nexus which does not seem to support SHA256 or SHA512. - The parent .pom has its <scm> section removed. It gets removed by the release plugin, not sure whether this is a feature or how it can be avoided. I will add the section again after the release. Kind regards, Tilmann
