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
