> I propose the following artifacts for release as 2.2.15.
> 
> sha1: 4ee4ceea28a1cb77b283c7ce0135340ddff02086
> Git: 
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.15-tentative
> Artifacts: 
> https://repository.apache.org/content/repositories/orgapachecassandra-1179/org/apache/cassandra/apache-cassandra/2.2.15/
> Staging repository: 
> https://repository.apache.org/content/repositories/orgapachecassandra-1179/
> 
> The Debian and RPM packages are available here: 
> http://people.apache.org/~mshuler
> 
> The vote will be open for 72 hours (longer if needed).


+1 nb


Checked the following…
 - all links work
 - git sha matches
 - the generated pom file doesn't contain snapshot dependencies 
 - source artefacts build
 - signatures checked
 

Problems
 - the rpm and deb artefacts have missing checksums or signatures. See 
http://people.apache.org/~mshuler/
 - build fails for this sha : 
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-2.2-artifacts/176/
 - when building the source artefact the binaries are labelled SNAPSHOT (even 
though this is just about the `-Drelease` flag)
 - artefacts are checksummed with md5 and sha1, instead of sha256/sha512. (the 
non-maven artefacts shouldn't be staged in nexus, and the md5 checksums should 
be removed manually before the vote starts.)
 - checksums are in wrong format (if they want to be easily checked with 
`shasum -c *.sha1`)
 - contains the snapshot dependency 
cassandra-driver-core-2.2.0-rc2-SNAPSHOT-20150617-shaded.jar


Questions
 - why are the source artefacts in both the nexus staging repository and in the 
rpm/deb repository?
 - do the signatures really need checksums?
 - apache projects (and the asf) don't usually permit binaries inside the 
source artefact. why do we permit this? i presume there's been some discussion 
on this in the past somewhere? maybe every jar file in the lib/ directory 
should be accompanied with the corresponding -sources.jar file?

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

Reply via email to