Hello. > > [...] > > see an explanation for why it is necessary > > (or even helpful) to include artefact hashes in the vote mail. > > > I agree and understand all your points here.
Well, I don't. An explanation would be useful indeed. > > Validating the svn revision for the dist repo [ ... vs ...] > > comparing the hashes of each file to a hash provided in > > the vote email. [...] > > I was merely trying to offer the opposing perspective of the other folks. Aren't we talking about a *requirement*? Referring to the "executive summary" above (as I understand it), from Mark's edited text, which information is necessary and sufficient for a vote? Also, isn't this discussion a rehash of my (recurrent) question about whether the hash checks should be automated? [I mean, isn't it sufficient that the RM would indicate in the vote email that the hash values stored in the "dist" area are the same as those generated by the build?] Regards, Gilles > > > [...] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
