+1
On Tue, Feb 1, 2022 at 9:10 AM Jeremy Mitchell <mitchell...@gmail.com> wrote: > > +1 > > On Mon, Jan 31, 2022 at 2:51 PM Zach Hoffman <zrhoff...@apache.org> wrote: > > > I've prepared a release for 6.1.0-RC2. Changes since RELEASE-6.0.2: > > > > > > https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC2 > > > > https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC2/CHANGELOG.md > > > > The artifacts are available for download at: > > > > https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC2/ > > > > BLAKE2 checksum: > > 35b73bea81f6550aeecb8e5a0e8776089b557fea135ffdd1c6bc022d3625e34941c834d55114cf7de594578ba4bbe1103d17ae9d3efc3b92ed52279d2c5b14e7 > > apache-trafficcontrol-6.1.0.tar.gz > > > > SHA512 checksum: > > be4cb2d99462cd92bb771705853381b8c6fd466d97ebbf273cc401e26629a56019838ba4a9993504780f5994f5005ae5f04d27587664ea3fe5113f816d6e1424 > > apache-trafficcontrol-6.1.0.tar.gz > > > > This corresponds to git refs: > > > > Hash: f8041b3b5d616003b32d7c0dc160f5f9621e5366 > > Tag: RELEASE-6.1.0-RC2 > > > > Which can be verified with the following command: > > > > $ git tag -v RELEASE-6.1.0-RC2 > > > > All code signing keys are available here: > > > > https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS > > > > Make sure you refresh from a key server to get all relevant signatures. > > > > The vote is open until 22:00 UTC on Thursday, February 3 and passes if a > > majority of at least 3 +1 PMC votes are cast. > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > -Zach > >
