Re: [VOTE] Bugtracking in Github Issues

+1 On Mon, Aug 28, 2017 at 4:43 PM, Jan van Doorn wrote: > +1 > > On Mon, 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. > > > > Now that we have write access to

Re: [VOTE] Bugtracking in Github Issues

+1 On Mon, 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. > > Now that we have write access to Github, we can move back to GH Issues for > bug tracking. > > This will be a better workflow

Re: [VOTE] Bugtracking in Github Issues

I thought we already had a vote on this? Maybe I am thinking of the "move to github" vote which I assumed to be all-encompassing. Anyway, +1 On Mon, Aug 28, 2017 at 10:43 AM, Dan Kirkwood wrote: > +1 > > On Mon, Aug 28, 2017 at 10:38 AM, Eric Friedrich (efriedri) >

[VOTE] Bugtracking in Github Issues

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 workflow because its one fewer tool and account to have to interact with. This will hopefully lower the bar

Re: [VOTE] Bugtracking in Github Issues

+1 On Mon, 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 workflow

Re: [VOTE] Bugtracking in Github Issues

+1 On Mon, Aug 28, 2017 at 10:44 AM, Dave Neuman wrote: > I thought we already had a vote on this? Maybe I am thinking of the "move > to github" vote which I assumed to be all-encompassing. > Anyway, +1 > > On Mon, Aug 28, 2017 at 10:43 AM, Dan Kirkwood

Re: [VOTE] Bugtracking in Github Issues

+1 On Mon, Aug 28, 2017 at 1:02 PM, Dewayne Richardson wrote: > +1 > > On Mon, Aug 28, 2017 at 10:44 AM, Dave Neuman wrote: > > > I thought we already had a vote on this? Maybe I am thinking of the > "move > > to github" vote which I assumed to be

Re: [VOTE] Bugtracking in Github Issues

I am -1 on this, but count take it with grain of salt since I am not developing code. I am generally system agnostic, but the maturity of Jira makes it a far superior tool for tracking, reporting, and staying organized. I would argue that since this is an open source project organization is

Re: [VOTE] Bugtracking in Github Issues

+1 > 1. Github * Has very little in the way of organizational options I view Github's simplicity as a plus. Jira has a steep learning curve, and is discouraging to potential new committers. Every separate tool we have (issues, wiki, docs) are more obstacles to new people. Github's built-ins

Re: Traffic Ops Configuration Management - Proposed Webex Meeting Tue 8/29/17 at 2 pm EST

Hello all, Following up on Ryan’s thread to provide a proposal for this discussion of config management, I tried to not make it a giant wall of text… but I’m not sure I succeeded. I wanted to also provide a proposed database schema but after a series of unfortunate events it no longer exists.

Re: Is multiple subdomains fully supported?

Hmm, no response… I think I should suppose no one is using multiple subdomains in production. Please response if I am wrong. Thanks, Zhilin On 8/25/17, 3:12 PM, "Zhilin Huang (zhilhuan)" wrote: Hi folks, The multiple subdomain (HOST_REGEXP) looks not working