Thank you all the response, they were very value feedback and very good
collection of questions which should be answered before going forward
with github issues.
Based on the feedback, I suggest the following:
1. don not enable the Github issues, yet
2. Create additional github action
I agree with many others here. I think the flexible query part is a very
useful feature from JIRA. If we have equivalent in gitgub issues, we can
try but may not be as immediate transition though.
I think people may need some time to get comfort with github
issues(personally I used(limited) git iss
Thanks for taking this up Marton.
I played around with Github issues, projects & milestones. I like the
simplicity of the UI and the one stop place for all things related to
development. However, the objection around the project management related
limitations of Github seem valid. I am OK with try
>From what I can tell above, one of the concerns might not be mentioned (or
I might have missed it) is migration cost for people who didn't have
experience on Github issue. For people who only worked on JIRA in the
past, github issues might affect contributions from those people.
An assumption he
Thanks Marton for starting the discussion.
I like the proposal of integrating issue tracking with the repo. It would
greatly help with keeping the discussions in one place and avoid the extra step
of creating a Jira.
I personally have never worked with Github issues and as such I am not famili
Thanks all for the discussion. I have similar concerns around function
completeness of Github issues. For example, are we going to miss JIRA's
flexible query with filtering and comprehensive role/permission management,
etc?
This may not be a fair comparison as JIRA is targeted as a project
managem
Thanks for starting this thread Marton.
I have worked with Github issues for other projects and find the
tracking rudimentary.
Basically absence of good queries, saving older queries, lack of
dashboards are my biggest objections to this.
I feel we can use some of the plugins with Github and
Marton, you should start a vote thread to get official consensus/objections.
> I feel that everybody is interested to try it out
Need more details here before proceeding.
Personally I am not in favor but if there is broad consensus from the community
I will not object.
Thanks,
Arpit
> On No
A quick summary about this thread:
1. Github seems to provide better user experience, and easier
contribution possibilities
2. If (!) we can live with the current structure of Github / limitations.
Based on the discussion from the last sync, I feel that everybody is
interested to try
hub.com/rancher/k3d/milestones
Marton
On 11/1/20 5:24 PM, Arpit Agarwal wrote:
Do you have an example of another project using milestones as you're
suggesting?
- Original message -
From: "Elek, Marton"
To: ozone-...@hadoop.apache.org
Subject: Re: [DISCUSS] Github issu
>
> >
> >
> >
> >
> > On 11/1/20 5:24 PM, Arpit Agarwal wrote:
> >> Do you have an example of another project using milestones as you're
> suggesting?
> >> - Original message -
> >> From: "Elek, Marton"
> >&
n 11/1/20 5:24 PM, Arpit Agarwal wrote:
>> Do you have an example of another project using milestones as you're
>> suggesting?
>> - Original message -
>> From: "Elek, Marton"
>> To: ozone-...@hadoop.apache.org
>> Subject: Re: [DISCUSS] Github is
arwal wrote:
Do you have an example of another project using milestones as you're suggesting?
- Original message -
From: "Elek, Marton"
To: ozone-...@hadoop.apache.org
Subject: Re: [DISCUSS] Github issues vs Jira issues
Date: Sunday, November 01, 2020 6:30 AM
Thanks the
Do you have an example of another project using milestones as you're suggesting?
- Original message -
From: "Elek, Marton"
To: ozone-...@hadoop.apache.org
Subject: Re: [DISCUSS] Github issues vs Jira issues
Date: Sunday, November 01, 2020 6:30 AM
Thanks the questions
Thanks the questions Arpit and Vivek.
I agree with you: the main question is how the existing workflows can be
mapped to the features of github issues.
We need to collect all the used workflows. I checked the two features
which you mentioned:
1. EPIC
Epics can be managed in Github with
15 matches
Mail list logo
