Yi-Sheng，
Good idea, I tracked it down with
https://issues.apache.org/jira/browse/HDDS-4415.
The mailing lists in
https://cwiki.apache.org/confluence/display/HADOOP/Ozone+Contributor+Guide
is updated to date.
Regards,
Sammi
On Thu, Oct 29, 2020 at 5:26 PM yisheng lien wrote:
> Thank you
This is Anecdotal data -- However I thought it might be useful to share.
In my current project(Unfortunately not open source, so I will not be able
share the data or screen shots) we use Github issues exclusively to track
all the issues.
Some things work very well -- So the pros are:
1. Very easy
Looks too unstructured. They are using labels for Issue type and priority. I
don’t see any priority field either. Not sure it is worth the energy to make
the switch.
> On Nov 1, 2020, at 9:34 AM, Elek, Marton wrote:
>
>
> Good question, I didn't do a research, yet.
>
> But I knew that Kube
Good question, I didn't do a research, yet.
But I knew that Kubernetes is a heavy Github user and I found it uses
milestones for versions:
https://github.com/kubernetes/kubernetes/milestones
Or k3s:
https://github.com/rancher/k3d/milestones
Marton
On 11/1/20 5:24 PM, Arpit Agarwal wr
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 Arpit and Vivek.
I
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
