[ 
https://issues.apache.org/jira/browse/CASSANDRA-14970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750179#comment-16750179
 ] 

Michael Shuler commented on CASSANDRA-14970:
--------------------------------------------

I tried switching the dependency from artifacts to release and tried a wildcard 
in the mvn-install task files, for example 
\{{file="${build.dir}/${final.name}-bin.tar.gz*"}}. I don't recall the exact 
error, but I just don't know ant well enough, so asked for some help.

Yes, we can just do the checksums and toss them in /dist/release/ in 
finish_release.sh, but that basically flaws the artifacts we're voting on. We 
should be voting on the entire artifact set, verified by the checksums and gpg 
signature. I'm just trying to look at the bigger picture and 
scripting/automating our release process to fix known broken things, as well as 
make it better/easier for multiple people to contribute to the release process, 
while trying to keep things stable/simple for user installs.

> New releases must supply SHA-256 and/or SHA-512 checksums
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-14970
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14970
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>            Reporter: Michael Shuler
>            Assignee: Michael Shuler
>            Priority: Blocker
>             Fix For: 2.1.21, 2.2.14, 3.0.18, 3.11.4, 4.0
>
>         Attachments: 
> 0001-Update-downloads-for-sha256-sha512-checksum-files.patch, 
> 0001-Update-release-checksum-algorithms-to-SHA-256-SHA-512.patch, 
> ant-publish-checksum-fail.jpg, build_cassandra-2.1.png, build_trunk.png
>
>
> Release policy was updated around 9/2018 to state:
> "For new releases, PMCs MUST supply SHA-256 and/or SHA-512; and SHOULD NOT 
> supply MD5 or SHA-1. Existing releases do not need to be changed."
> build.xml needs to be updated from MD5 & SHA-1 to, at least, SHA-256 or both. 
> cassandra-builds/cassandra-release scripts need to be updated to work with 
> the new checksum files.
> http://www.apache.org/dev/release-distribution#sigs-and-sums



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to