Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

[Leif Hedstrom]

> On Jan 27, 2017, at 9:46 AM, Dan Kirkwood  wrote:
> 
> +1
> 
> -- was assuming as release manager I didn't get a vote,  but not true?

Everyone gets to vote :). If you are a PPMC member, your vote is binding. We 
should encourage non-PPMC members to vote as well, some of the best problem 
reports tend to come from those who did not actively work on the code.

Fwiw, being the RM is not “special”, you are in theory just packaging up all 
the work the community has put together.  Excluding the RM from voting seems 
unfair :).

Cheers,

— Leif


> 
> I tested:
> -  signature and checksums good
> -  build from gitrepo and RC9 tag
> - scanning source with `rat` tool shows no license issues
> -  install traffic_ops on new Centos 7.2 VM
> -  setup new mysql,  loaded with test data
> -  login from UI,  navigating parts of UI
> 
> 
> On Wed, Jan 25, 2017 at 9:15 AM, Dan Kirkwood  wrote:
>> Hello All,
>> 
>> I've prepared another release for v1.8.0 (RC9)
>> 
>> Changes since 1.7.0:
>> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC9
>> 
>> This corresponds to git:
>>  Hash: 2301659f699948d9944cc07bc92b9f6a56bc4678
>>  Tag: RELEASE-1.8.0-RC9
>> 
>> Which can be verified with the following:git tag -v RELEASE-1.8.0-RC9
>> 
>> My code signing key is available here:
>> http://keys.gnupg.net/pks/lookup?search=0x4587A8F0=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/RC9
>> 
>> More Apache License compliance changes are included in this RC.
>> Several third-party javascript files were removed that were deemed
>> unused.
>> 
>> The vote will remain open until Friday,  Jan 27, 2017.
>> 
>> Thanks!

Re: Traffic Monitor Roadmap

[Jan van Doorn]

+1

Nice work, Rob.

Cheers,
JvD

> On Jan 26, 2017, at 12:54 PM, Robert Butts  wrote:
> 
> As some of you know, we've been rewriting Traffic Monitor in Go. The
> rewrite adds non-lockstep polling, as well as generally giving us more
> flexibility and making it easier to add other big features in the future.
> The rewrite is currently at
> https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor/experimental
> 
> I want to share our tentative roadmap, to see if anyone has objections or
> suggestions.
> 
> The rewrite is nearing completion, and very close to parity with the
> current version. We're now ready to start the process of integrating it
> into the build scripts, and replacing the current version in the repository.
> 
> The plan is to move the code to
> `incubator-trafficcontrol/traffic_monitor_golang` very shortly, probably
> tomorrow if no one objects. This is necessary to avoid countless
> infrastructure hacks and workarounds, primarily with the build scripts.
> 
> We'll then begin testing in QA and then production systems. Once we've
> verified it works to replace the current monitor without issue, we'll move
> it to `incubator-trafficcontrol/traffic_monitor`, and move the current app
> to `incubator-trafficcontrol/traffic_monitor_old`, with all the build
> scripts and documentation updated accordingly. Then,
> `incubator-trafficcontrol/traffic_monitor_old` will be considered
> Deprecated and removed in the next major version (remaining in the git
> history forever, of course, if anyone needs to clone or fork it).
> 
> There are no firm timelines for any of this, except the impending move to a
> root project directory. We'll take as long as necessary to test and verify.
> Traffic Monitor will continue to be versioned with Traffic Control.