[ https://issues.apache.org/jira/browse/OAK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197626#comment-16197626 ]
Davide Giannella commented on OAK-6650: --------------------------------------- [~reschke] bq. Is this what I was supposed to test? testing the full release cycle is rather difficult so we can really test only this bits. However a another pair of eyes on this few lines of patches could ease any future troubles. If the patches look good for you I will move this foreword so that you can apply the counterpart for jackrabbit. Otherwise the checkrelease script as modified now will fail for JR releases. > new release checksum requirements > --------------------------------- > > Key: OAK-6650 > URL: https://issues.apache.org/jira/browse/OAK-6650 > Project: Jackrabbit Oak > Issue Type: Improvement > Reporter: Davide Giannella > Assignee: Davide Giannella > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8 > > Attachments: OAK-6650-checkrelease.diff > > > As of various SHA algorithm the Apache policies around signatures and > checksums changed requiring to specify the sha algorithm as part of the file > extension: sha1, sha256, sha512. > http://www.apache.org/dev/release-distribution#sigs-and-sums > currently Oak signs with sha-1 and we should at least change the file > extension > h3. impacted areas > - release process (pom.xml) > - check release > - html download page -- This message was sent by Atlassian JIRA (v6.4.14#64029)