Re: [VOTE] Resolution for Traffic Control graduation to TLP

> On Apr 2, 2018, at 2:11 PM, David Neuman wrote: > > Dear Traffic Control community members: > > I would like to call a vote on the resolution for Traffic Control to > graduate from to an Apache TLP. We have already voted on whether or not we > should start the

Re: [VOTE] Traffic Control graduation to TLP

+1 — Leif > On Mar 1, 2018, at 08:41, Dave Neuman wrote: > > Hey All, > > After a great discussion amongst the Apache Traffic Control PPMC, reviewing > the graduation checklist[1], updating the podling status page[2], and > updating the project website to ensure the whimsy

Re: [VOTE] CHANGELOG.md file (second try)

> On Jan 9, 2018, at 10:22 AM, Dave Neuman wrote: > > Looks like this thread died over the holidays. Let me try to bring it back > up before we cut a 2.2 branch. > Can you please respond with *just* the following: > > [X] +1 to adding a changelog.MD file > [] -1 to adding

Re: Traffic Control with ATS 7+

> On Nov 21, 2017, at 9:45 PM, Mark Torluemke wrote: > > I agree -- supporting 3 ATS major versions is likely more work than it's > worth. Traffic Ops core should continue to move towards being cache > software agnostic. > > Having said that, we have some logic today

Re: [VOTE] Bugtracking in Github Issues

> On Aug 29, 2017, at 4:47 PM, Leif Hedstrom <zw...@apache.org> wrote: > > >> On Aug 28, 2017, at 10:38 AM, Eric Friedrich (efriedri) <efrie...@cisco.com> >> wrote: >> >> We currently use JIRA Issues to track all of the Traffic Control bugs. >&

Re: [VOTE] Bugtracking in Github Issues

> On Aug 28, 2017, at 10:38 AM, Eric Friedrich (efriedri) > wrote: > > We currently use JIRA Issues to track all of the Traffic Control bugs. > > Now that we have write access to Github, we can move back to GH Issues for > bug tracking. > > This will be a better

Re: Public CI Builds for Traffic Control

and we get 95% of the benefit without solving any of > the actually hard problems. > > We'd need a host, though. > > On Tue, Mar 14, 2017 at 5:06 PM Leif Hedstrom <zw...@apache.org> wrote: > >> >>> On Mar 13, 2017, at 8:44 AM, Chris Lemmons <alfic...@gm

Re: Public CI Builds for Traffic Control

> On Mar 13, 2017, at 8:44 AM, Chris Lemmons wrote: > > To me, the key features of CI are that a) it builds each branch > automatically, b) notifies affected parties when all is not well, and c) > manages the artefacts in a reasonable way. Additionally, we're a lot more >

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

> On Feb 21, 2017, at 9:06 AM, Dan Kirkwood wrote: > > Hello Incubator PMC, > +1 (binding) — Leif

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

> On Feb 16, 2017, at 12:39 PM, Dan Kirkwood wrote: > > We have 4 +1 already, so I'm declaring RC10 as passed! Fwiw, that’s not generally how things work. You had stated that the vote was very short (“end of the day”), so at a minimum you need to let that time pass.

Re: clang-analyzer on the CI

> On Feb 1, 2017, at 3:21 PM, Leif Hedstrom <zw...@apache.org> wrote: > > Hi all, > > I’ve enabled the Clang analyzer builds for the CI. I’d highly recommend that > if it fails, you look into why, at least for PRs on master. Unfortunately, I > haven’t figur

clang-analyzer on the CI

Hi all, I’ve enabled the Clang analyzer builds for the CI. I’d highly recommend that if it fails, you look into why, at least for PRs on master. Unfortunately, I haven’t figured out a good way to expose the actual details in some meaningful way, I’m still working on that. In the mean time, if

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

> 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

Re: [VOTE] incubator-trafficcontrol-1.8.0-RC6

> On Jan 6, 2017, at 2:15 PM, Dan Kirkwood wrote: > > Hello All, > > I've prepared another release for v1.8.0 (RC6) > > Changes since 1.7.0: > https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC6 > >

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC4

> On Dec 13, 2016, at 7:47 AM, Dan Kirkwood wrote: > > So that makes us +1 overall, since you're the only vote :-) Eeep. Where are the mentor votes? :) I’m traveling and in meetings this week, but if you are extending the vote deadling, I can try to take a look tomorrow

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC3

> On Dec 8, 2016, at 12:29 PM, Eric Friedrich (efriedri) > wrote: > > Any chance we could start running RAT as part of our CICD builds? > > I could probably set something up in our private Jenkins if theres not a > better option. +1 as well. Fwiw, we do this nightly

Re: Apache license in source files

> On Dec 5, 2016, at 3:48 PM, Dan Kirkwood wrote: > > Hi all.. We haven't really established a process for this, but to > keep in compliance with Apache license guidelines, each source file > should have the Apache license comment -- normally at the head of the > file,

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC3

> On Dec 2, 2016, at 5:57 PM, Dan Kirkwood wrote: > > Thanks again for the feedback, Leif..There is a .rat_excludes > file at the top level, but it looks like we didn't get it fully > populated. The .json files should certainly be excluded.. Oh, but it was not in

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC3

> On Dec 1, 2016, at 4:02 PM, Dan Kirkwood wrote: > > Hello All, > > I've prepared another release for v1.8.0 (RC3) > > Changes since 1.7.0: > https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC3 > > This corresponds to git: > Hash:

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC2

> On Dec 1, 2016, at 12:46 PM, Phil Sorber wrote: > > http://www.apache.org/dev/release-signing.html#basic-facts > > Missing checksums for the artifacts. > > And for the record, I am still not liking the RPM's as release artifacts, > but I'll let the IPMC weigh in on that.

Re: Help the poor RMs

> On Nov 11, 2016, at 1:28 PM, David Neuman wrote: > > I actually don't think we can do milestones, labels, or assignees in github > anymore. We lost that when we moved to the incubator github. :( > But we should mark Jiras accordingly and open a Jira for a PR

Help the poor RMs

Please make an effort to mark GitHub PRs (and Jiras) with relevant information. In Github, you have Milestones (versions), Labels (components etc.) as well as assignee you can use. You can also add PRs to the projects, to help with back ports etc. Same with Jira, at a minimum add the

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC1

> On Nov 8, 2016, at 6:46 PM, Eric Friedrich (efriedri) > wrote: > > Hey Dan- > I haven’t looked at the RPMs yet, but I think we also need to put up a > package for astats. > > A few other things: > - Package name should have “incubating” in it > - Need signatures

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC1

> On Nov 8, 2016, at 3:27 PM, Dan Kirkwood wrote: > > Hello All, > > I've prepared a release for v1.8.0 (RC1) > > Changes since 1.7.0: > https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC1 > >

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC1

> On Nov 8, 2016, at 3:27 PM, Dan Kirkwood wrote: > > Hello All, > > I've prepared a release for v1.8.0 (RC1) > > Changes since 1.7.0: > https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC1 > > This corresponds to git: > Hash: