I've prepared a release for 6.0.1-RC0. Changes since RELEASE-6.0.0:

        
https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.0...RELEASE-6.0.1-RC0
        
https://github.com/apache/trafficcontrol/blob/RELEASE-6.0.1-RC0/CHANGELOG.md

The artifacts are available for download at:

        https://dist.apache.org/repos/dist/dev/trafficcontrol/6.0.1/RC0/

BLAKE2 checksum:
c1cf6ee38b4071fc2b403dc3dcbad7dc6a9a93cb98d6f35accd1fd64f4c6db3657b0f5db9766708c7f71659ef0f796eedcd6ac7eafac2f1aa56b477ff7a76aa5
  apache-trafficcontrol-6.0.1.tar.gz

SHA512 checksum:
d51c2e34aaafc77ecb5af21c464a118a660846f9f8ea5d64b014142e61af165bda4319251294cf1e8121d0a27175567753aa6410d5f10c81a84381af343f9d0d
  apache-trafficcontrol-6.0.1.tar.gz

This corresponds to git refs:

        Hash: 1ed2964d16618aeebef142b01a538336a44d07dd
        Tag: RELEASE-6.0.1-RC0

Which can be verified with the following command:

        $ git tag -v RELEASE-6.0.1-RC0

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.

Please test and cast your votes as early as possible. The vote is open until 
22:00 UTC on Monday, November 8.
        [ ] +1 approve
        [ ] +0 no opinion
        [ ] -1 disapprove (and reason why)

-Zach

--

Changelog for 6.0.1-RC0:

Added
        #2770 Added validation for httpBypassFqdn as hostname in Traffic Ops

Fixed
        #6125 - Fix /cdns/{name}/federations?id=# to search for CDN.
        #6283 - The Traffic Ops Postinstall script will work in CentOS 7, even 
if Python 3 is installed
        #5373 - Traffic Monitor logs not consistent
        #6197 - TO /deliveryservices/:id/routing makes requests to all TRs 
instead of by CDN.
        Traffic Ops: Sanitize username before executing LDAP query

Changed
        #5927 Updated CDN-in-a-Box to not run a Riak container by default but 
instead only run it if the optional flag is provided.
        Changed the DNSSEC refresh Traffic Ops API to only create a new change 
log entry if any keys were actually refreshed or an error occurred (in order to 
reduce changelog noise)

Reply via email to