On Mon, Jul 23, 2018 at 4:57 PM, yuhang xiu wrote:
> Agree ‘&READY-TO-CLOSE&’.
> Constantly try the best solution.
> :)
+1
>
> 2018-07-23 16:52 GMT+08:00 Yong Zhu :
>
>> On Fri, Jul 20, 2018 at 4:01 PM Huxing Zhang wrote:
>>
>> > Hi,
>> >
>> > On Thu, Jul 19, 2018 at 6:11 PM, yuhang xiu wrote:
Agree ‘&READY-TO-CLOSE&’.
Constantly try the best solution.
:)
2018-07-23 16:52 GMT+08:00 Yong Zhu :
> On Fri, Jul 20, 2018 at 4:01 PM Huxing Zhang wrote:
>
> > Hi,
> >
> > On Thu, Jul 19, 2018 at 6:11 PM, yuhang xiu wrote:
> > > I think it is better.
> > > :)
> > >
> > > 2018-07-19 11:04 GMT+0
On Fri, Jul 20, 2018 at 4:01 PM Huxing Zhang wrote:
> Hi,
>
> On Thu, Jul 19, 2018 at 6:11 PM, yuhang xiu wrote:
> > I think it is better.
> > :)
> >
> > 2018-07-19 11:04 GMT+08:00 Yong Zhu :
> >
> >> How about 'NEED-CLOSE' ?
>
> This keyword is not special enough, which may introduces false pos
Seems it difficult to solve..
Maybe directly @ committers?
2018-07-20 16:00 GMT+08:00 Huxing Zhang :
> Hi,
>
> On Thu, Jul 19, 2018 at 6:11 PM, yuhang xiu wrote:
> > I think it is better.
> > :)
> >
> > 2018-07-19 11:04 GMT+08:00 Yong Zhu :
> >
> >> How about 'NEED-CLOSE' ?
>
> This keyword is n
Hi,
On Thu, Jul 19, 2018 at 6:11 PM, yuhang xiu wrote:
> I think it is better.
> :)
>
> 2018-07-19 11:04 GMT+08:00 Yong Zhu :
>
>> How about 'NEED-CLOSE' ?
This keyword is not special enough, which may introduces false positive[1].
For examples, the following query will match some unrelated issu
I think it is better.
:)
2018-07-19 11:04 GMT+08:00 Yong Zhu :
> How about 'NEED-CLOSE' ?
>
> On Wed, Jul 18, 2018 at 6:38 PM yuhang xiu wrote:
>
> > I agree.
> > But, is '&READY-TO-CLOSE&' too long to use ? How about a abbreviation
> like
> > &RTC& or sth?
> >
> > (Sorry about last mail..)
> >
How about 'NEED-CLOSE' ?
On Wed, Jul 18, 2018 at 6:38 PM yuhang xiu wrote:
> I agree.
> But, is '&READY-TO-CLOSE&' too long to use ? How about a abbreviation like
> &RTC& or sth?
>
> (Sorry about last mail..)
>
> 2018-07-18 18:37 GMT+08:00 yuhang xiu :
>
> > I agree.
> > But, is '&READY-TO-CLOS
I agree.
But, is '&READY-TO-CLOSE&' too long to use ? How about a abbreviation like
&RTC& or sth?
(Sorry about last mail..)
2018-07-18 18:37 GMT+08:00 yuhang xiu :
> I agree.
> But, is '&READY-TO-CLOSE&' too long to use ? How about a abbreviation
> like &RTC& or
>
> 2018-07-18 18:22 GMT+08:00
I agree.
But, is '&READY-TO-CLOSE&' too long to use ? How about a abbreviation like
&RTC& or
2018-07-18 18:22 GMT+08:00 Huxing Zhang :
> Hi,
>
> I just have a new idea!
>
> For an issue that is ready to be closed, anyone can comment with
> special characters, say, &READY-TO-CLOSE&.
>
> So commit
Hi,
I just have a new idea!
For an issue that is ready to be closed, anyone can comment with
special characters, say, &READY-TO-CLOSE&.
So committers can search the issue with the special characters, and
deal with it.
https://github.com/apache/incubator-dubbo/issues?utf8=%E2%9C%93&q=is%3Aissue+
I've updated the issue report template.
On Wed, Jul 18, 2018 at 10:07 AM Ian Luo wrote:
> +1, maybe we should make it clear in issue report template.
>
> On Tue, Jul 17, 2018 at 4:08 PM Andrea Del Bene
> wrote:
>
>> hi!
>>
>>
>> 2. Some of issues are not clearly described, making us hard to
>>
+1, maybe we should make it clear in issue report template.
On Tue, Jul 17, 2018 at 4:08 PM Andrea Del Bene
wrote:
> hi!
>
>
> 2. Some of issues are not clearly described, making us hard to
> > reproduce, or reported long time ago. For these kind of issues, I
> > think simply reply with "Thanks
+1 merge PR more later, more difficult.
At 2018-07-17 21:51:34, "Huxing Zhang" wrote:
>On Tue, Jul 17, 2018 at 4:08 PM, Andrea Del Bene wrote:
>> hi!
>>
>>
>> 2. Some of issues are not clearly described, making us hard to
>>> reproduce, or reported long time ago. For these kind of issues, I
>>> t
On Tue, Jul 17, 2018 at 4:08 PM, Andrea Del Bene wrote:
> hi!
>
>
> 2. Some of issues are not clearly described, making us hard to
>> reproduce, or reported long time ago. For these kind of issues, I
>> think simply reply with "Thanks for your question, would you please
>> try the latest version?
hi!
2. Some of issues are not clearly described, making us hard to
> reproduce, or reported long time ago. For these kind of issues, I
> think simply reply with "Thanks for your question, would you please
> try the latest version? I am going to close this issue now. Feel free
> to reopen it if th
On Tue, Jul 10, 2018 at 11:39 PM, Mark Thomas wrote:
> On 10/07/18 07:04, jun liu wrote:
>> Hi All,
>>
>> Now the community has become very active, pull requests and issues are being
>> reported in a certain amount every day, in contrast, our response seems not
>> fast enough and issues bumped u
On 10/07/18 07:04, jun liu wrote:
> Hi All,
>
> Now the community has become very active, pull requests and issues are being
> reported in a certain amount every day, in contrast, our response seems not
> fast enough and issues bumped up.
>
> I've thought of a duty table for temporarily solvi
Let's triage issues daily, and tag the issues with 'good first issue' or
'help wanted'. It is committer's duty so let's put more focus on it.
Thanks,
-Ian.
On Tue, Jul 10, 2018 at 2:04 PM jun liu wrote:
> Hi All,
>
> Now the community has become very active, pull requests and issues are
> being
Hi All,
Now the community has become very active, pull requests and issues are being
reported in a certain amount every day, in contrast, our response seems not
fast enough and issues bumped up.
I've thought of a duty table for temporarily solving this problem, committers
on duty are respons
19 matches
Mail list logo
