Re: jira backlogs

It showed cached data for me until I logged in, then it refreshed on the next view. Not very intuitive, but if you know you need to be logged in it's probably just an annoyance that it might show old, cached data. On Tue, May 19, 2015 at 10:29 AM, Neha Narkhede wrote: > Just got a chance to take

Re: jira backlogs

Just got a chance to take a look at this, so it takes me directly to JIRA. However, I think I know what you had in mind for this, Joel and it seems very useful :-) On Tue, May 19, 2015 at 10:21 AM, Joel Koshy wrote: > Looks like a bug - maybe browser caching. The previous jira/confluence > integ

Re: jira backlogs

Looks like a bug - maybe browser caching. The previous jira/confluence integration allowed you to refresh the table on the page directly. I will ping infra. For now I just changed it to use the link view, which just takes you to the jira. On Tue, May 19, 2015 at 9:23 AM, Jun Rao wrote: > Thanks,

Re: jira backlogs

Thanks, Joel. Do you know why it doesn't seem to reflect the recent changes? For example, kafka-1928 still has jkreps listed as the reviewer. Jun On Mon, May 18, 2015 at 3:10 PM, Joel Koshy wrote: > Here is (roughly) what I had in mind for this: > > https://cwiki.apache.org/confluence/display/K

Re: jira backlogs

I forgot to add - I believe you need to be logged into jira at the time you view the page. The search basically filters by patch-available, non-empty reviewer and ordered by updated date. Thanks, Joel On Mon, May 18, 2015 at 03:10:03PM -0700, Joel Koshy wrote: > Here is (roughly) what I had in

Re: jira backlogs

Here is (roughly) what I had in mind for this: https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review#Patchsubmissionandreview-Reviewqueue Earlier versions of wiki/jira integration were much better in that the inline table had pagination within the wiki page itself. Unfortun

Re: jira backlogs

Gwen, Kafka jira is configured to allow contributors to edit and transition issues. So, not sure why you can't assign yourself as a reviewer. If you still have the problem, could you file an infra jira? Thanks, Jun On Wed, Apr 8, 2015 at 9:41 AM, Gwen Shapira wrote: > One more thing: I curren

Re: jira backlogs

> > We can do both of course, but I think apache infra already has > what is needed for this. Yes, if Apache INFRA has this, great. I would pick something that is a *push* mechanism and leave the *pull* as an option for proactive folks to refer to. Honestly, today you can go and save the JIRA que

Re: jira backlogs

The weekly email sounds good, but I would much rather if that were integrated into the wiki/jira system than run a custom script on non-apache infra. We did something similar during 0.8 replication development where we embedded JQL links in the wiki and had a nice dashboard view of jiras on a wiki

Re: jira backlogs

One more thing: I currently can't assign myself as a reviewer. Do you need to add me to a new JIRA group for that? Or maybe give this capability to all contributors? On Wed, Apr 8, 2015 at 9:38 AM, Gwen Shapira wrote: > Thanks Neha :) > I'm glad to hear those reviews are useful. > > I created KA

Re: jira backlogs

Thanks Neha :) I'm glad to hear those reviews are useful. I created KAFKA-2107 to track the new email script. I agree it will be helpful and I'm sure someone will pick it up soon :) Gwen On Wed, Apr 8, 2015 at 9:07 AM, Neha Narkhede wrote: > To clarify, reviewers don't have to be committers.

Re: jira backlogs

To clarify, reviewers don't have to be committers. If as a non-committer reviewer, you feel that the patch is ready for commit, feel free to ping/tag one of the committers. This

Re: jira backlogs

Hi Jun, Do reviewers have to be committers? I'll be happy to review patches in areas that I'm familiar with, if this makes life easier for committers and helps us get improvements in faster. Gwen On Tue, Apr 7, 2015 at 11:10 PM, Jun Rao wrote: > Hi, everyone, > > Currently, we have accumulated