Thanks for preparing the RC ocket8888! Since I think this is the first time we've attempted a release with convenience binaries, can you share what you've done to ensure license compliance with those new artifacts?
I'll do my best to get a vote together on the release in the next 3 days. --Eric On Tue, Oct 20, 2020 at 5:49 PM ocket 8888 <[email protected]> wrote: > Hello All, > > I've prepared a release for v5.0.0-RC0 > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Approve the release > > [ ] -1 Do not release this package because ... > > Changes since 4.1.0: > https://github.com/apache/trafficcontrol/compare/4.1.0...RELEASE-5.0.0-RC0 > > This corresponds to git: > Hash: d5ee85fdcd36b998573e8819b63c51764093dff9 > Tag: RELEASE-5.0.0-RC0 > > Which can be verified with the following: git tag -v RELEASE-5.0.0-RC0 > > My code signing key is available here: > > https://keys.gnupg.net/pks/lookup?search=0xF5D560A373B76FA302A95DBFCDFE430685982C95&fingerprint=on&op=index > > Make sure you refresh from a key server to get all relevant signatures. > Also, their SSL key seems messed up right now, so you might get a browser > warning. > > The source .tgz file, pgp signature (.asc signed with my key from > above), and sha512 checksums are provided here: > > https://dist.apache.org/repos/dist/dev/trafficcontrol/5.0.0/RC0 > > > Thanks! > ocket8888 [email protected] >
