+1 on this, signature and hashes validate. -- Thanks, Jeff
On Mon, Jun 5, 2017 at 7:03 AM, Eric Friedrich (efriedri) <efrie...@cisco.com> wrote: > Hello All, > > I've prepared the next candidate release for incubator-trafficcontrol v2.0.0 > (RC3) > > Changes since 1.8.0: > https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC3 > > This corresponds to git: > Hash: 795ea3adf2003dd27523b6b9ff4691f23d41ce30 > Tag: RELEASE-2.0.0-RC3 > > Which can be verified with the following: git tag -v RELEASE-2.0.0-RC3 > > My code signing key is available here: > http://pgp.mit.edu/pks/lookup?op=get&search=0xF2200BAB9AB7BDD5 > > and here: > https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS > > Make sure you refresh from a key server to get all relevant signatures. > > The source .tar.gz file, pgp signature (.asc signed with my key from > above), and md5 and sha512 checksums are provided here: > https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.0.0/RC3<https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.0.0/RC2> > > > The vote will remain open until Thursday, June 8, 2017. > > This RC fixes some packaging issues in RC2, there are no other changes. The > git tag hash is the same, but due to changes in the tarball the release > signatures HAVE changes. > > Thanks, > Eric Friedrich
