We could do a trial period of GitHub issues for the accumulo sub-repos
(accumulo-website, accumulo-examples...) then after a month or two decide
to switch or not.  That way we won't have duplicate issues or the confusion
of having 2 trackers for one repository.

On Wed, Feb 14, 2018 at 6:12 PM, Mike Walch <mwa...@apache.org> wrote:

> +1 I think it makes sense to try out GitHub before shutting off JIRA. This
> period could be limited to a month or two.
>
> On Wed, Feb 14, 2018 at 5:59 PM, Christopher <ctubb...@apache.org> wrote:
>
> > What if we had an interim transition period, tentatively using GitHub to
> > determine it's suitability for our workflows, and shut off JIRA later?
> >
> > On Wed, Feb 14, 2018 at 5:51 PM Josh Elser <els...@apache.org> wrote:
> >
> > > I disagree with Mike in that I don't find JIRA to be so painful that it
> > > necessitates us changing, but I wouldn't block a move to GH issues if
> we
> > > turn off our JIRA use.
> > >
> > > On 2/14/18 4:29 PM, Mike Drob wrote:
> > > > @josh - How do you feel about move from JIRA to GH Issues completely?
> > > >
> > > > On Wed, Feb 14, 2018 at 3:26 PM, Josh Elser <els...@apache.org>
> wrote:
> > > >
> > > >> I believe I already stated -1 the last time this was brought up.
> > > >>
> > > >> Using two issue trackers is silly.
> > > >>
> > > >>
> > > >> On 2/14/18 3:30 PM, Mike Walch wrote:
> > > >>
> > > >>> I want to enable GitHub issues for Accumulo's repos. This is not to
> > > >>> replace
> > > >>> JIRA but to give contributors more options for issue tracking.
> Unless
> > > >>> there
> > > >>> are objections, I will create an infra ticket this week.
> > > >>>
> > > >>>
> > > >
> > >
> >
>

Reply via email to