accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject Re: Additional options for issue tracking
Date Thu, 15 Feb 2018 03:29:46 GMT
Can you elaborate on what kind of human controls you mean? What if a user
finds the GH issues and creates an issue there? What action should the
developers take?

On Wed, Feb 14, 2018 at 10:27 PM Josh Elser <elserj@apache.org> wrote:

> I didn't ask for automated controls here -- human controls are fine.
>
> I have already said I am -1 on two concurrent issue trackers. If
> developers want to evaluate them, that's fine.
>
> On 2/14/18 10:12 PM, Christopher wrote:
> > I don't think we have the ability to lock out non-committers from
> creating
> > new GH issues if we enable them, nor do I think it would make sense to do
> > so, since that's a valuable use case to consider during any trial period
> > before shutting off JIRA.
> >
> > As for switching immediately to GH issues for non-primary repo (-website,
> > -examples, -docker, etc...) I think that makes sense since those are
> > already confusing when filed in the JIRA mixed in with the main repo's
> > issues.
> >
> > On Wed, Feb 14, 2018 at 9:25 PM Josh Elser <elserj@apache.org> wrote:
> >
> >> I am OK with committers ONLY using GH issues on all repos (with clear
> >> guidance as to what the heck the project is doing) or doing a
> >> full-switch on the other repos.
> >>
> >> On 2/14/18 7:00 PM, Mike Miller wrote:
> >>> 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 <mwalch@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 <ctubbsii@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 <elserj@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 <elserj@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.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message