The release dir looked fine to me. Were you looking at maven? Those are automatically generated during the upload and we don’t have explicit control over them. I’ve spent hours just trying to get rid of the hash files for the signatures :(
Anthony > On Mar 20, 2018, at 3:18 PM, Dan Smith <dsm...@pivotal.io> wrote: > > It looks like we are still generating .md5 files. That doesn't necessarily > need to hold up this release (you could just delete them from SVN), but > we're not supposed to be distributing .md5 files anymore. > > http://www.apache.org/dev/release-distribution#sigs-and-sums > > -Dan > > On Tue, Mar 20, 2018 at 3:09 PM, Swapnil Bawaskar <sbawas...@pivotal.io> > wrote: > >> This is the first release candidate for Apache Geode, version 1.5.0. >> Thanks to all the community members for their contributions to this >> release! >> >> *** Please download, test and vote by Friday, March 23, 1500 hrs >> US Pacific. *** >> >> It fixes 234 issues. release notes can be found at: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> projectId=12318420&version=12342395 >> >> Note that we are voting upon the source tags: rel/v1.5.0.RC1 >> https://github.com/apache/geode/tree/rel/v1.5.0.RC1 >> https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1 >> >> Commit ID: >> 4ef51dacd79ff69336fb024f3d4b0727cccc1e90 (geode) >> 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples) >> >> Source and binary files: >> https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1 >> >> Maven staging repo: >> https://repository.apache.org/content/repositories/orgapachegeode-1038 >> >> >> Geode's KEYS file containing PGP keys we use to sign the release: >> https://github.com/apache/geode/blob/develop/KEYS >> >> Release Signed with Key: pub 4096R/18F902DB 2016-04-07 >> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB >>
