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
On Sat, Jul 16, 2011 at 12:30 PM, Jeremy Hanna
wrote:
> I don't see a way in DatabaseDescriptor to set the rpc_timeout_in_ms via jmx.
>
> It doesn't seem possible right now.
>
> Is there any reason why that couldn't be set via jmx? It seems like a
> rolling restart to update that is pretty heavy
DataStax has had requests for something like this. It seems like
something that would be generally useful for the community though.
Regarding twitter, I'm not sure a twitter account should be required
to get that information. I think you can follow a twitter account as
an rss feed though, so that
On Mon, Jul 18, 2011 at 10:32 AM, Sylvain Lebresne wrote:
> That being said, I could understand that some people may find it
> cleaner to have a
> separate announce list and it is not something unheard of, so I'm ok
> with that if enough
> people thinks it's a good idea.
Ditto.
> - should it be
I have mixed feeling about that.
On the one side, I agree with Gary that it doesn't add any real value.
There is twitter,
and we use consistent tagged subjects for release email, so it's easy
to subscribe
to the user list and set up a filter.
That being said, I could understand that some people m
I think a lot of people follow cassandra on twitter. However I don't think it
would be a big deal to email both user@ and announcements@ when a new release
is out, if people don't mind the extra list.
Nick - is this from people asking about this?
On Jul 18, 2011, at 9:50 AM, Gary Dusbabek wrot
I am developing a new API call which will read results from multiple
nodes. I am first sending a message to each node and maintain a list of
handlers, one for each message.
However, after all requests are sent, I can only call the handlers' get()
function sequentially, wait for each to finish and
Following @cassandra on twitter or a google alert would be simple enough I
think.
Gary.
On Mon, Jul 18, 2011 at 14:26, Nick Bailey wrote:
> What do we think about having a separate mailing list for just
> cassandra related announcements. The main purpose being announcing new
> releases once the
I think this is a good idea. It would be helpful for a lot of people who
don't want to monitor dev, but they want the artifacts that come out of it.
On 7/18/11 7:26 AM, Nick Bailey wrote:
What do we think about having a separate mailing list for just
cassandra related announcements. The main pu
What do we think about having a separate mailing list for just
cassandra related announcements. The main purpose being announcing new
releases once they pass a vote and are put up on the website. I think
there is a desire for a way to be informed when new releases are
available without sifting thro
15 matches
Mail list logo
