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 Jira to provide
better integrations.
On 09/11/20 9:40 pm, Arpit Agarwal wrote:
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 Nov 9, 2020, at 4:23 AM, Elek, Marton <e...@apache.org> wrote:
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 it out, but I feel some concerns to do the decision right now. Hard to
imagine the final workflow after years of Jira-based Hadoop development (even
if the patch-handling already migrated)
My proposal:
1. Start a two month trial period
2. Make the Jira creation for new PRs optional.
3. Start to use proper tags (priority, version) for pull requests. (I can create
an additional Github action to fill the defaults --> no big change).
4. Enable Github issues in Ozone project and use it with a few new issues.
(Doesn't required to create all the new issues in Github, just a few minor one,
to test it, understand the limitations)
After the two month trial period, we can make a decision, and:
1. Migrate old Jira issues to Github (if Github is prefered)
2. Migrate the experimental Github issues to Jira, and create Jira issues for
PRs when missing. (if Jira is preferred)
+1: Use Github wiki for wiki pages.
What do you think?
Thanks,
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
