nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Burgess <mattyb...@gmail.com>
Subject Re: [VOTE] Incorporate SHA256 part of release process
Date Thu, 14 Apr 2016 01:33:04 GMT
+1


> On Apr 13, 2016, at 6:13 PM, Aldrin Piri <aldrinpiri@gmail.com> wrote:
> 
> This was mentioned in the vote thread for the RC2 release and wanted to
> separate it out to keep the release messaging streamlined. As mentioned by
> Andy, the MD5 and SHA1 are subject to collisions. From another viewpoint, I
> like having this as part of the official release process as I typically
> generate this myself when updating the associated Homebrew formula with no
> real connection to the artifacts created other than me saying so.
> 
> The drawback is that the Maven plugins that drives the release
> unfortunately does not support SHA-256.[1] As a result this would fall on
> the RM to do so but could easily be added to the documentation we have
> until the linked ticket is resolved.
> 
> This vote will be a lazy consensus and remain open for 72 hours.
> 
> 
> [1] https://issues.apache.org/jira/browse/MINSTALL-82

Mime
View raw message