-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Where is the release signature file that goes with the public key?
On 11/30/11 6:30 PM, Franklin, Matthew B. wrote: > Discussion thread for vote on 0.6-incubating release candidate. > > Note, there were two staging repos created during the release process. I am > unsure why this happened, but I did have a network hiccup while the release > script was running, so maybe that was the issue. All of the artifacts appear > to have made it fine, but it would be good to have a second pair of eyes > check that. > > Also, I forgot to create a combined release with the updated master pom > containing the metadata that has Sean as a committer/PPMC member listed. > > For more information on the release process, checkout - > http://www.apache.org/dev/release.html > http://incubator.apache.org/guides/releasemanagement.html > > Some of the things to check before voting are: > - can you run the demo binaries > - can you build the contents of source-release.zip and svn tag > - do all of the staged jars/zips contain the required LICENSE, NOTICE and > DISCLAIMER files > - are all of the staged jars signed and the signature verifiable > - is the signing key in the project's KEYS file and on a public server -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO3QvmAAoJEEfVXEODPFIDqqEH/0DFUzIbAghqvz8k7/5rCe4F 7D6dwpYfImbShDchVirQfP+Mei0Ug3Ar6f1/VDWpgW7DEF9tLkiZb8kylC/7pjNj gm/fJ6nt4LtDi69k4DXxD2x+tcIQBgY2DdX2Avak++1nw237cS/emGUJTkANyWN8 QQW3TtG5h5bj8T4osoJkiX1/fdf8FOgSd6u4CN8yJCXJ5LBiXcD8ku9rOUokZdFl r/jnsPzBHj2A+hcIWyWGAdUrS049fetG0ltkif88IpOaSiWBu326WexOzLGw0WVY rhXdkcV/30PZL5l20SlWTpeZX6DqCBanFO2DglBog2cx4uh9A5II4uDttVmW5FQ= =dIJA -----END PGP SIGNATURE-----
