Thanks all. Started a VOTE around this.
If you can chime in with your +1s there as well, it will be great!
On Fri, Jul 16, 2021 at 8:31 PM Gary Li wrote:
> +1 for option B.
>
> On Sat, Jul 17, 2021 at 9:51 AM Udit Mehrotra wrote:
>
> > +1 for option B. For A, I will need more data points to
+1 for option B.
On Sat, Jul 17, 2021 at 9:51 AM Udit Mehrotra wrote:
> +1 for option B. For A, I will need more data points to convince myself if
> GitHub issues will provide all the issue tracking functionality that Jira
> provides today.
>
> Thanks,
> Udit
>
> On Fri, Jul 16, 2021 at 2:33 PM
+1 for option B. For A, I will need more data points to convince myself if
GitHub issues will provide all the issue tracking functionality that Jira
provides today.
Thanks,
Udit
On Fri, Jul 16, 2021 at 2:33 PM Vinoth Chandar wrote:
> Looks like we can start with B has a lot of support.
> I
Looks like we can start with B has a lot of support.
I will start a VOTE on B alone and we can proceed if the VOTE passes.
On Fri, Jul 16, 2021 at 8:05 AM Nishith wrote:
> +1 for option B.
>
> > On Jul 15, 2021, at 10:50 PM, Bhavani Sudha
> wrote:
> >
> > Completely agree on B. On A I feel
+1 for option B.
> On Jul 15, 2021, at 10:50 PM, Bhavani Sudha wrote:
>
> Completely agree on B. On A I feel the necessity to centralize everything
> in one place but also without losing the capabilities of Jira. I think we
> will have to explore tools in eitherways.
>
> Thanks,
> Sudha
>
Completely agree on B. On A I feel the necessity to centralize everything
in one place but also without losing the capabilities of Jira. I think we
will have to explore tools in eitherways.
Thanks,
Sudha
On Thu, Jul 15, 2021 at 10:42 PM vino yang wrote:
> +1 for option B.
>
> Best,
> Vino
>
>
+1 for option B.
Best,
Vino
Sivabalan 于2021年7月16日周五 上午10:35写道：
> +1 on B. Not sure on A though. I understand the intent to have all in
> one place. but not very sure if we can get all functionality (version,
> type, component, status, parent- child relation), etc ported over to
> github. I
+1 on B. Not sure on A though. I understand the intent to have all in
one place. but not very sure if we can get all functionality (version,
type, component, status, parent- child relation), etc ported over to
github. I assume labels are the only option we have to achieve these.
Probably, we
Based on this, I will start consolidating more of the cWiki content to
github wiki and master branch?
JIRA vs GH Issue still probably needs more feedback. I do see the tradeoffs
there.
On Fri, Jul 9, 2021 at 2:39 AM wei li wrote:
> +1
>
> On 2021/07/02 03:40:51, Vinoth Chandar wrote:
> > Hi
+1
On 2021/07/02 03:40:51, Vinoth Chandar wrote:
> Hi all,
>
> When we incubated Hudi, we made some initial choices around collaboration
> tools of choice. I am wondering if there are still optimal, given the scale
> of the community at this point.
>
> Specifically, two points.
>
> A) Our
Any more strong opinions around these?
On Mon, Jul 5, 2021 at 7:43 AM Vinoth Chandar wrote:
> I had similar views on A actually. JIRA is pretty powerful, queryable.
> But, I convinced myself on labelling and then building out dashboards using
> SQL (for reports/analytics).
> Still having one
I had similar views on A actually. JIRA is pretty powerful, queryable. But,
I convinced myself on labelling and then building out dashboards using SQL
(for reports/analytics).
Still having one place for issues/prs. For releases, we can
directly leverage milestones.
We can definitely prioritize B
Just to mention there are some GitHub plugin brings JIRA features to GH
issues. This one for example is free for open source.
https://www.zenhub.com/pricing
On Fri, Jul 2, 2021 at 8:58 PM Navi Brar
wrote:
> Hi,
>
>
> +1 on B
>
>
> But I have a slightly orthogonal view on A. I think jira
Hi,
+1 on B
But I have a slightly orthogonal view on A. I think jira should stay. It
provides a lot more visibility on the issue management. You can link PRs,
wikis, releases etc easily which everyone will have to dig through the comments
in github or every github issue might end up having
+1 for both A and B. Makes sense to centralize bug tracking and RFCs in github.
Balaji.V
On Friday, July 2, 2021, 06:44:06 PM PDT, Vinoth Chandar
wrote:
Raymond - +1 on your thoughts.
Once we have more voices and alignment, we can do one final RFC on cWiki
covering everything.
Can
+1 for both A and B
Also a related suggestion:
we can put the release notes and new feature highlights in the release
notes section in GitHub releases instead of separately writing them in the
asf-site
On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason
wrote:
> +1 for complete Github migration.
Hi all,
When we incubated Hudi, we made some initial choices around collaboration
tools of choice. I am wondering if there are still optimal, given the scale
of the community at this point.
Specifically, two points.
A) Our issue tracker is JIRA, while we just use Github Issues for support
17 matches
Mail list logo
