Hi Igniters,
By common efforts from maintainers, committers and experienced
contributors, it was possible to reduce the number of PA tasks
- waiting for review to 88,
- with no activity for 1 month and waiting for review to 24.
'No activity' tasks are more than a quarter from all patches
Hi Igniters,
I want to raise up this thread again. If your ticket seems to be stuck in
review process, please write. I will try to help.
Can't promise it would be fast, but I hope together we can find a solution
for each particular case.
Sincerely,
Dmitriy Pavlov
чт, 8 февр. 2018 г. в 2:08,
Anyway, your suggestion requires to have self-disciplined committers that will
be keeping track of the tickets they promised to review.
I’m ready to propose a guideline here but the committers have to be committed
to that. Otherwise, I’ll just waste my time.
—
Denis
> On Feb 7, 2018, at 1:41
Periodic punches can frustrate committers, and also it's unpleasant for
contributors. Most IP->PA transitions are commented with something like
"John Doe, this awesome feature is ready and needs your review." Maybe it's
better to adopt following rule of thumb? If the change is clean and
I guess it’s all about discipline.
Committers need to walk-through a list of the pull-request regularly while
contributors have to remind of a pending pull-request periodically. So both
parts have to be proactive.
Another approach is to find a volunteer from the community who will keep an eye
Fix Version should not be a required field, uncheduled tickets are
perfectly normal.
On Mon, Feb 5, 2018 at 4:20 PM, Vyacheslav Daradur
wrote:
> Hi Pavel,
>
> I've noticed that usually abandoned tickets are tickets without
> specified "Fix Version", otherwise tickets should
Hi Pavel,
I've noticed that usually abandoned tickets are tickets without
specified "Fix Version", otherwise tickets should be viewed once at
least by release manager for moving to next release.
Should we do "Fix Version" as required field?
On Mon, Feb 5, 2018 at 3:44 PM, Дмитрий Рябов
Dmitry, there are 103 tickets for Cassandra [1] and 120 for Zookeeper [2].
[1]
https://issues.apache.org/jira/browse/CASSANDRA-14132?jql=project%3Dcassandra%20AND%20status%3D"Patch%20Available"%20AND%20updated%20<%20-30d
[2]
Fixed links:
https://issues.apache.org/jira/issues/?jql=project%3Dignite%20AND%20status%3D%22Patch%20Available%22%20AND%20updated%20%3C%20-30d
Hi Denis,
There is an interesting aspect of this issue for me.
How close is Ignite community in this metric (not reviewed/not merged
tickets) to other Apache communities? For example, to Cassandra.
Sincerely,
Dmitriy Pavlov
пн, 5 февр. 2018 г. в 14:51, Pavel Tupitsyn :
Bumping the thread.
Denis Magda, as a PMC chair, can you please look into this?
On Tue, Jan 30, 2018 at 5:26 PM, Pavel Tupitsyn
wrote:
> Igniters,
>
> We have *almost 60* of PATCH AVAILABLE tickets that are inactive for more
> than a month:
>
Igniters,
We have *almost 60* of PATCH AVAILABLE tickets that are inactive for more
than a month:
https://issues.apache.org/jira/issues/?filter=12333285=project%3Dignite%20AND%20status%3D%22Patch%20Available%22%20AND%20updated%20%3C%20-30d
(JQL: project=ignite AND status="Patch Available" AND
12 matches
Mail list logo