Unfortunately, I am -1 on this release. I have found 2 issues that I believe need to be addressed before we release 3.0.0. They are: https://github.com/apache/trafficcontrol/issues/2919 - Traffic Ops in not creating the url_sig location parameter when a new DS is created with URL Siging keys which causes ORT to fail unless the param is created manually; and https://github.com/apache/trafficcontrol/issues/2918 - Traffic Ops is not associated the hdr_rw location param to any profiles when you create a new DS with an Edge Header rewrite.
Both of these issues have manual workarounds but since they are regressions is feel that we should fix them instead of relying on a manual work-around. Thanks, Dave On Wed, Oct 10, 2018 at 11:35 AM Gelinas, Derek <[email protected]> wrote: > Hello All, > > I've prepared a release for v3.0.0-RC0 > > 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-RC0 > > > > This corresponds to git: > Hash: 66199be84c02ea62a952168ce8c9e68e0d2db79a > Tag: RELEASE-3.0.0-RC0 > > Which can be verified with the following: git tag -v RELEASE-3.0.0-RC0 > > > > 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/RC0/ > > > > Thanks! > >
