On 2/15/18 12:28 PM, Christopher wrote:
Want to spin out a DISCUSS on the desire to switch, Mike Walch? That
seems to me like it should be the next step.
I thought that's what we were doing.:)
This isn't tagged with DISCUSS in the subject (which I know some
subscribers of our list filter on)
On Thu, Feb 15, 2018 at 11:31 AM Josh Elser wrote:
>
> On 2/15/18 11:26 AM, Keith Turner wrote:
> > On Thu, Feb 15, 2018 at 11:01 AM, Josh Elser wrote:
> >> We tell users that try to file issues on the "unsupported" issue tracker
> >> that they've created the issue in the wrong place and point t
On 2/15/18 11:26 AM, Keith Turner wrote:
On Thu, Feb 15, 2018 at 11:01 AM, Josh Elser wrote:
We tell users that try to file issues on the "unsupported" issue tracker
that they've created the issue in the wrong place and point them to the
right issue tracker.
Personally I think that is ok for
On Thu, Feb 15, 2018 at 11:01 AM, Josh Elser wrote:
> We tell users that try to file issues on the "unsupported" issue tracker
> that they've created the issue in the wrong place and point them to the
> right issue tracker.
Personally I think that is ok for a short period. Its like driving on
a
The organic solution seems to have arisen from the Apache Software
Foundation by way of their issue tracking system.
Others have stated concerns already, so aside from doing this "for the
people," would this also address a problem?
"The contribution workflow using Jira is longer and more painful
We tell users that try to file issues on the "unsupported" issue tracker
that they've created the issue in the wrong place and point them to the
right issue tracker.
On 2/14/18 10:29 PM, Christopher wrote:
Can you elaborate on what kind of human controls you mean? What if a user
finds the GH i
> 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
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 wrote:
> I d
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 wrote:
> I didn't ask for automated controls here -- human controls are fine.
>
> I have a
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 creati
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-
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, a
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, Mik
+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 wrote:
> What if we had an interim transition period, tentatively using GitHub to
> determine it's suitability for our workflows, and
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 wrote:
> I disagree with Mike in that I don't find JIRA to be so painful that it
> necessitates us changing,
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, 20
Nobody thought it was silly when we were using more than one review
mechanism (reviewboard + GitHub + comments on patches attached to JIRA).
I don't think enabling the feature is the same as mandating anybody use it,
especially for the secondary repos like the website, the docker repo, and
examples
+1 to enabling the feature... so we can see how it works, and especially so
we can use it with the sub-project repos, like the website and examples,
whose issues are confusing when mixed in with the main Accumulo repo's
issues.
I'm not in favor of mandating a switch to using these GitHub features.
@josh - How do you feel about move from JIRA to GH Issues completely?
On Wed, Feb 14, 2018 at 3:26 PM, Josh Elser 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 Git
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 o
The contribution workflow using Jira is longer and more painful than the
workflow using GitHub issues. This is not a big deal for large
contributions but it adds up when you make a lot of small contributions.
Creating a Jira account and using Jira is also a roadblock for Apache
newbies. We should m
While I love github issues, I do have concerns about 2 separate issue
tracking systems. Can you elaborate on what you are trying to solve?
Let's make sure we give everyone time to discuss before making this change.
On Wed, Feb 14, 2018 at 3:31 PM Mike Walch wrote:
> I want to enable GitHub issu
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.
23 matches
Mail list logo
