I'm -1 on the release because of issue
https://github.com/apache/trafficcontrol/issues/3304 . The conversion to go
from perl has inconsistent strong/weak typing implementation inside the json
payloads. The Traffic Portal is the primary client that's been checked and
converted to strong typing
Do you have an example of an endpoint that is in the 3.0 release that will
not work now because of this bug? I think we should take a look at what
is effected and make our decision from there. A release is not guaranteed
to have no known issues, but we do need to decide if we can live with the
k
The issue cited was where I found it because I had automation that had weakly
typed payloads as was permissible via perl. Once I upgraded to a version that
had been converted to Go, the automation broke. I can fairly easily fix it in
my code, but API are contracts and I object to retroactively
+1
Verified the following:
- sha checksum correct
- gpg signature correct
- RELEASE-3.0.0-RC4 tag signed correctly
- BUILD_NUMBER file indicates the correct commit count and hash
- all components build with `./pkg -v`
- saw same problem with `weasel`, but it's pointing out files in `.m2` dir
(from
