Right, that's what we typically use as a "needs review" dashboard.
On Mon, Jul 18, 2011 at 3:08 PM, Jim Ancona wrote:
> Thanks for the quick response! So the correct procedure is to attach
> the patch and make sure the issue is in "Patch Available" status?
>
> I'll try to do that next time.
>
> J
Thanks for the quick response! So the correct procedure is to attach
the patch and make sure the issue is in "Patch Available" status?
I'll try to do that next time.
Jim
On Mon, Jul 18, 2011 at 4:03 PM, Jonathan Ellis wrote:
> I think the "in progress" status is preventing Patch Available someh
I had to reassign it myself to mark it patch available, then assign
back to Jim. Stupid jira.
On Mon, Jul 18, 2011 at 3:03 PM, Jonathan Ellis wrote:
> I think the "in progress" status is preventing Patch Available somehow?
>
> In any case, I've asked Pavel to review. Thanks for following up, Ji
I think the "in progress" status is preventing Patch Available somehow?
In any case, I've asked Pavel to review. Thanks for following up, Jim.
On Mon, Jul 18, 2011 at 2:57 PM, Brandon Williams wrote:
> You should mark it 'patch available' so someone will know to review it.
>
> On Mon, Jul 18, 2
You should mark it 'patch available' so someone will know to review it.
On Mon, Jul 18, 2011 at 2:55 PM, Jim Ancona wrote:
> I attached a patch to CASSANDRA-2717 a week or so ago. Should I be
> doing anything else to make sure it gets reviewed?
>
> Jim
>
> On Tue, Jul 5, 2011 at 11:31 AM, Jonatha
I attached a patch to CASSANDRA-2717 a week or so ago. Should I be
doing anything else to make sure it gets reviewed?
Jim
On Tue, Jul 5, 2011 at 11:31 AM, Jonathan Ellis wrote:
> I regularly get requests for pointers to "starter" tickets. I suggest
> we tag such tickets as LHF (for low-hanging
Excellent idea indeed, I have been looking for such tickets as well :)
I take the chance to introduce myself to the list btw, I'm currently
getting my toes wet in Cassandra, developing (mostly) in python, and
willing to contribute - I'm not there yet though; will have a look at
the LHF tickets for
Good idea.
On Wed, Jul 6, 2011 at 8:40 AM, David Boxenhorn wrote:
> You should include the first link in the second, maybe as a bullet in step
> 4, e.g.:
>
> - If you're looking for ticket to work on, check out our low-hanging-fruit
> list:
> https://issues.apache.org/jira/secure/IssueNavigator.j
You should include the first link in the second, maybe as a bullet in step
4, e.g.:
- If you're looking for ticket to work on, check out our low-hanging-fruit
list:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf
On Tue, Jul 5
I regularly get requests for pointers to "starter" tickets. I suggest
we tag such tickets as LHF (for low-hanging fruit). I've tagged four
such to get started:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+12310865+AND+labels+%3D+lhf
I'll try to keep t
10 matches
Mail list logo
