>
>>>>>>>> On Wed, Jun 12, 2019 at 11:51 PM Marco Gaido <
>>>>>>>> marcogaid...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Dongjoon,
>>>>>>>>> Thanks for the proposal! I
1:51 PM Marco Gaido
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Dongjoon,
>>>>>>>> Thanks for the proposal! I like the idea. Maybe we can extend it to
>>>>>>>> component too and to some jira labels suc
h to highlight in PRs too. My only concern is that in many cases
>>>>>>> JIRAs
>>>>>>> are created not very carefully so they may be incorrect at the moment of
>>>>>>> the pr creation and it may be updated later: so keeping them in
<mailto:r...@databricks.com>> wrote:
> Seems like a good idea. Can we test this with a component first?
>
> On Thu, Jun 13, 2019 at 6:17 AM Dongjoon Hyun <mailto:dongjoon.h...@gmail.com>> wrote:
> Hi, All.
>
> Since we use both Apache JIRA and GitHub actively
gt; JIRAs
>>>>>> are created not very carefully so they may be incorrect at the moment of
>>>>>> the pr creation and it may be updated later: so keeping them in sync may
>>>>>> be
>>>>>> an extra effort..
>>>>>>
>>&
they may be incorrect at the moment of
>>>>> the pr creation and it may be updated later: so keeping them in sync may
>>>>> be
>>>>> an extra effort..
>>>>>
>>>>> On Thu, 13 Jun 2019, 08:09 Reynold Xin, wrote:
>>>
t;>>> Seems like a good idea. Can we test this with a component first?
>>>>>
>>>>> On Thu, Jun 13, 2019 at 6:17 AM Dongjoon Hyun
>>>>> wrote:
>>>>>
>>>>>> Hi, All.
>>>>>>
>>>>>&g
>>>
>>>> Seems like a good idea. Can we test this with a component first?
>>>>
>>>> On Thu, Jun 13, 2019 at 6:17 AM Dongjoon Hyun
>>>> wrote:
>>>>
>>>>> Hi, All.
>>>>>
>>>>> Since
gt;>> On Thu, Jun 13, 2019 at 6:17 AM Dongjoon Hyun
>>> wrote:
>>>
>>>> Hi, All.
>>>>
>>>> Since we use both Apache JIRA and GitHub actively for Apache Spark
>>>> contributions, we have lots of JIRAs and PRs consequently. One spec
gt;
>>> Hi, All.
>>>
>>> Since we use both Apache JIRA and GitHub actively for Apache Spark
>>> contributions, we have lots of JIRAs and PRs consequently. One specific
>>> thing I've been longing to see is `Jira Issue Type` in GitHub.
>>>
&g
Hi, All.
>>
>> Since we use both Apache JIRA and GitHub actively for Apache Spark
>> contributions, we have lots of JIRAs and PRs consequently. One specific
>> thing I've been longing to see is `Jira Issue Type` in GitHub.
>>
>> How about exposing JIRA issue
thing I've been longing to see is `Jira Issue Type` in GitHub.
>
> How about exposing JIRA issue types at GitHub PRs as GitHub `Labels`?
> There are two main benefits:
> 1. It helps the communication between the contributors and reviewers with
> more information.
> (In some c
, wrote:
> Hi, All.
>
> Since we use both Apache JIRA and GitHub actively for Apache Spark
> contributions, we have lots of JIRAs and PRs consequently. One specific
> thing I've been longing to see is `Jira Issue Type` in GitHub.
>
> How about exposing JIRA issue types at Gi
Hi, All.
Since we use both Apache JIRA and GitHub actively for Apache Spark
contributions, we have lots of JIRAs and PRs consequently. One specific
thing I've been longing to see is `Jira Issue Type` in GitHub.
How about exposing JIRA issue types at GitHub PRs as GitHub `Labels`? There
ar
14 matches
Mail list logo
