Changing my vote to +1. I checked build process, and Traffic Ops file generation.
All ATS files are the same, except some ordering in parent.config that is expected, and some local patches / extensions we have. CRConfig is identical according to the UI diff tool, although I did find httpsPort is missing in the new release - opened https://issues.apache.org/jira/browse/TC-104 <https://issues.apache.org/jira/browse/TC-104> for that, but Neuman says that’s not a show stopper, as it defaults to 443. Rgds, JvD > On Jan 18, 2017, at 5:02 PM, Jan van Doorn <[email protected]> wrote: > > I am +0; > > I built all components and am working on a script to do a pre vs post upgrade > comparison on our production data. Almost there, got held up on Traffic Vault > (don’t ask). > > So I’ll let it go if others feel confident, but would ask for a day extension > if they aren’t. > > Rgds, > JvD > > >> On Jan 13, 2017, at 1:57 PM, Dan Kirkwood <[email protected]> wrote: >> >> Hello All, >> >> I've prepared another release for v1.8.0 (RC7) >> >> Changes since 1.7.0: >> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC8 >> >> This corresponds to git: >> Hash:597e7795c48ab65fe57175642973481b9dc020e6 >> Tag: RELEASE-1.8.0-RC8 >> >> Which can be verified with the following: git tag -v RELEASE-1.8.0-RC8 >> >> My code signing key is available here: >> http://keys.gnupg.net/pks/lookup?search=0x4587A8F0&op=vindex >> >> Make sure you refresh from a key server to get all relevant signatures. >> >> The source .tar.gz file, pgp signature (.asc signed with my key from >> above), and md5 and sha1 checksums are provided here: >> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC8 >> >> More Apache License compliance changes are included in this RC as well >> as one critical regression from 1.7: >> https://issues.apache.org/jira/browse/TC-97 >> >> The vote will remain open until Wednesday, Jan 18, 2017. >> >> Thanks! >
