Not sure where to jump in on this thread, but, I do not have any preference for one tool or the other at this point - but would really just want one. My concerns:
Would we export the current Jira issues to GH Issues? Would we ""lose"" past history, or would I need to search one tool or two to see if a previous issue was opened or addressed. Would we, at a minimum, port open issues to the new tool? Are we putting too many eggs in a single GH basket - what if we wanted / needed to switch repositories in the future for any reason? Would this make it harder for others that are using other Apache projects (say HADOOP, ZOOKEEPER) to determine, report or track issues across multiple projects? What if they are contributors? Are there now different work-flows for Accumulo than for other Apache projects? Does it make contributing to Accumulo easier, harder, different? I'm not opposed to a change if there are clear, demonstrable benefits beyond personal preferences - but I also have an affinity to continuity and consistency. Ed Coleman -----Original Message----- From: Christopher [mailto:ctubb...@apache.org] Sent: Wednesday, February 14, 2018 6:00 PM To: dev@accumulo.apache.org Subject: Re: Additional options for issue tracking 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. > >>> > >>> > > >
