Also, another thing to note would be that Github issues don't support Epics.
We will have to create milestones to track big features and their progress or use a third-party Github action like this - https://github.com/marketplace/actions/epic-issues-for-github. Regards, Vivek Subramanian On Wed, Oct 28, 2020 at 8:48 AM Arpit Agarwal <aagar...@cloudera.com.invalid> wrote: > Doesn't look like GitHub issues supports custom fields. Does it support > basics like resolution/fix version? I checked out Druid's GitHub issues, > everything seems to be tacked on using labels. > > > On Wed, Oct 28, 2020 at 1:09 AM Elek, Marton <e...@apache.org> wrote: > > > Hi, > > > > The new Apache Ozone project requires new git repositories / issue > > tracker / wiki namespaces. > > > > And it seems to be a good opportunity to think about the used issue > > tracker / issue workflow. > > > > > > I suggest to consider using Github for issue tracking and wiki instead > > of Jira / Confluence. > > > > > > > > Advantages: > > > > * Better integration between PRs and issues (and between issues and > > other Github features) > > > > * Current workflow would be simplified (doesn't require to create > > boilerplate Jira issue for each new PR) > > > > * Easier for for contributors (doesn't require to create jira user, > > request to assign permission to be an assignee...) > > > > * Easier to follow discussions (I know some issues where half of the > > discussion was under the PR the other half was under the Jira) > > > > * Easier to follow contribution statistics (enough to query github api) > > > > > > > > Disadvantage: > > > > * Finding / reading old issue still require Jira (but we can migrate > > the open issues if we need them) > > > > I don't think it's a big deal as we already have some issues at other > > places (for example children of HDFS-7240). > > > > > > > > What are your opinions? > > > > > > Note: There are Apache projects which already uses Github instead of > > Jira (Superset, Druid and many smaller incubator projects) > > > > Marton > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: ozone-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: ozone-dev-h...@hadoop.apache.org > > > > >
