On Mon, May 18, 2015 at 3:05 PM, Dave Brosius
wrote:
> You can assign your self to an issue in JIRA (if you can't let us know,
> and we can add you as a contributor).
>
Personally, I prefer this step be done on commit to avoid people being on
the contributor list without actually producing code.
Thanks!
Not sure if i get fully your question, but you can see the various
branches, and tags in use here
https://git-wip-us.apache.org/repos/asf?p=cassandra.git
Typically, if you are targeting a patch for an older release, the patch
should be against that older branch, and hopefully it will
Hi,
I want to submit patch for Cassandra JIRA tickets.
I have some questions:
1. As per http://wiki.apache.org/cassandra/HowToContribute, we need to clone
trunk and provide patch on that. So, I need to understand how this patch is
going to be merged in 2.0.x and 2.1.x ?
2. Where can I get the d
