cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Yudovin <vla...@winguzone.com>
Subject Re: CASSANDRA-8596
Date Tue, 29 Nov 2016 08:56:59 GMT
Hi guys, thanks for answer!



Actually the last activity on this ticket was my question 

Does this issue exist with other snitches? How can they benefit from my solution?




Also before working on ticked or prepare patch it's good to know if it's needed at all. ;-)

Look at https://issues.apache.org/jira/browse/CASSANDRA-8945 It was Resolved to "Not A Problem"
without any discussion.



We made this and other fixes in our own Cassandra build, but if things are silently denied
obviously it's not stimulate donation and participation, as it takes more time and energy
than just to fix it for us only.



Best regards, Vladimir Yudovin, 

Winguzone - Cloud Cassandra Hosting






---- On Tue, 29 Nov 2016 03:45:59 -0500 Oleksandr Petrov &lt;oleksandr.petrov@gmail.com&gt;
wrote ----




I would recommend several things that could help this (and probably many 

other patches that accidentally went under radar) to get accepted. It's 

hard to keep an enormous amount of issues in memory, so we try to rely on 

simple rules that help everyone to see current status and understand what 

to do next with the ticket: 

 

 * if you are planning to work on ticket, assign it to yourself. 

Sometimes it's also good to comment on it (if there was previous activity), 

as someone else might be already working on it but forgot to mention it or 

assign it. Doesn't happen often though. 

 * If you're working on it, put it into "work in progress" status. 

 * If you have finished working on the patch and think it's ready for 

review, put it into "ready for review" state. 

 * (bonus) ping someone on cassandra-dev IRC channel to get your patch 

submitted for CI. Most of time however, this will be done by reviewer 

anyways. But having a passing build is always reassuring. 

 

I know that committers (and active contributors) are frequently reviewing 

"ready for review" tickets and try to provide feedback. Relying only on 

ticket comments is a bit hard, since it's too easy to lose track of them. 

 

Sometimes it's possible that the next person who can review the ticket will 

only have time in a couple of weeks. Everyone does their best. But if you 

feel that it went forgotten, just leave another comment. 

 

Hope this helps! 

 

On Tue, Nov 29, 2016 at 9:19 AM Vladimir Yudovin &lt;vladyu@winguzone.com&gt; 

wrote: 

 

&gt; Hi, 

&gt; 

&gt; 

&gt; 

&gt; in the light of broader community involvement I would like to bring 

&gt; attentions to the https://issues.apache.org/jira/browse/CASSANDRA-8596 I 

&gt; open with proposed patch. 

&gt; 

&gt; It's stuck for almost 1.5 years. 

&gt; 

&gt; 

&gt; 

&gt; I would like to help with Cassandra development and improvement, and I 

&gt; have several other fixes, some has JIRA, some not. 

&gt; 

&gt; 

&gt; 

&gt; Best regards, Vladimir Yudovin, 

&gt; 

&gt; Winguzone - Cloud Cassandra Hosting 

&gt; 

&gt; 

&gt; 

&gt; 

&gt; 

&gt; -- 

Alex Petrov 







Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message