+1 I verified: - RELEASE-6.0.x-RC6 tag present and signed - all packages build with `./pkg -v` from source tarball - sha512 matches - gpg signature verified - all rpms built above install on CentOS 7.4 - traffic_ops `postinstall -defaults=to.cfg` produces a good template - (after edits to to.cfg) `postinstall -cfile=to.cfg` initializes db correctly - traffic_ops and traffic_portal start up - able to login to traffic_portal and do some basic views/edits - from traffic_portal : `/api/1.3/about` displays correct version number (matches RELEASE-... tag)
On Wed, Feb 13, 2019 at 9:48 AM Gelinas, Derek <[email protected]> wrote: > Hello All, > I've prepared a release for v3.0.0-RC6 > The vote is open for at least 72 hours and passes if a majority of at > least 3 +1 PPMC votes are cast. > [ ] +1 Approve the release > [ ] -1 Do not release this package because ... > Changes since 2.2 > https://github.com/apache/trafficcontrol/compare/2.2.x...RELEASE-3.0.0-RC6 > This corresponds to git: > Hash: eca5d609dc5877e9abc075c0228e6e400473f564 > Tag: RELEASE-3.0.0-RC6 > Which can be verified with the following: git tag -v RELEASE-3.0.0-RC6 > My code signing key is available here: > http://keys.gnupg.net/pks/lookup?search=0x05BE71D9&op=vindex > Make sure you refresh from a key server to get all relevant signatures. > 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/3.0.0/RC6/ > Thanks! > Derek > >
