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 for
+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 because its one fewer t
+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 bec
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)
> wrote:
> > We currently use
+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 Github, we can move ba
+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 wrote:
>
> > +1
> >
> > On Mon, Aug 28,
+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 all-encompassing.
> > Anyway, +1
> >
> > On Mo
upp...@comcast.com>
From: Dan Kirkwood
Reply-To: "dev@trafficcontrol.incubator.apache.org"
Date: Monday, August 28, 2017 at 10:50 AM
To: "dev@trafficcontrol.incubator.apache.org"
Subject: Re: [VOTE] Bugtracking in Github Issues
+1
On Mon, Aug 28, 2017 at 10:38 AM
> Reply-To: "dev@trafficcontrol.incubator.apache.org" <
> dev@trafficcontrol.incubator.apache.org>
> Date: Monday, August 28, 2017 at 10:50 AM
> To: "dev@trafficcontrol.incubator.apache.org" <
> dev@trafficcontrol.incubator.apache.org>
> Subje
> 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 workflow because its one fe
> On Aug 29, 2017, at 4:47 PM, Leif Hedstrom wrote:
>
>
>> 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
Thanks Leif-
I’ll check with the Incubator gurus. We already pulled the trigger, so at
this point its more about asking for forgiveness.
—Eric
On Aug 29, 2017, at 6:47 PM, Leif Hedstrom
mailto:zw...@apache.org>> wrote:
On Aug 28, 2017, at 10:38 AM, Eric Friedrich (efriedri)
mailto:efrie...@
+1 but the fact that only committers can be assigned to issues is a big
problem in my opinion.
On Tue, Aug 29, 2017 at 7:16 PM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:
> Thanks Leif-
> I’ll check with the Incubator gurus. We already pulled the trigger, so
> at this point its more
13 matches
Mail list logo
