退订。





At 2018-12-05 14:09:18, "ShaoFeng Shi" <shaofeng...@apache.org> wrote:
>Hi folks, thanks for your comment. Since there is no objection, I reported
>a JIRA to the infra team:
>
>https://issues.apache.org/jira/browse/INFRA-17362
>
>Best regards,
>
>Shaofeng Shi 史少锋
>Apache Kylin PMC
>Work email: shaofeng....@kyligence.io
>Kyligence Inc: https://kyligence.io/
>
>Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
>Join Kylin user mail group: user-subscr...@kylin.apache.org
>Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>
>
>
>
>JiaTao Tao <taojia...@gmail.com> 于2018年12月3日周一 下午12:10写道:
>
>> +1
>>
>> ShaoFeng Shi <shaofeng...@apache.org> 于2018年12月3日周一 上午1:46写道:
>>
>> > Hello Kylin developers,
>> >
>> > After we enable the git box for Kylin code repository, when there is a PR
>> > merged, the "ASF Github Bot" will insert the git diff to the associated
>> > JIRA. We noticed this function will make the JIRA very long when the code
>> > change is big. Besides, when cherry-picking the change to another branch,
>> > it will append again. This makes it is too hard for a human to read the
>> > JIRA, the important message may be overlooked.
>> >
>> > A typical sample is this:
>> > https://issues.apache.org/jira/browse/KYLIN-3187
>> >
>> > My proposal is, stopping sync the code change from GitHub to JIRA; Only
>> > keep necessary notifications like "A PR is created/closed" etc. For the
>> > code change, people should go to GitHub code history, not JIRA.
>> >
>> > Please express your ideas; If no objection in the next couple of days, we
>> > will raise a change request to the infrastructure team.
>> >
>> > Thanks for your input!
>> >
>> > Best regards,
>> >
>> > Shaofeng Shi 史少锋
>> > Apache Kylin PMC
>> > Work email: shaofeng....@kyligence.io
>> > Kyligence Inc: https://kyligence.io/
>> >
>> > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
>> > Join Kylin user mail group: user-subscr...@kylin.apache.org
>> > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>> >
>>
>>
>> --
>>
>>
>> Regards!
>>
>> Aron Tao
>>

Reply via email to