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 automerge
forward.
If you know this is not the case, then please supply different patch
files for branches.
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).
It may be wise (depending on the issue) to discuss in general how you
will attack the problem first, to get feedback, so
you don't spend alot of energy first only to have to potentially redo,
or such.
But yes, then attach the patch file. *.txt are preferred as they can be
viewed directly from the web.
HTH,
dave
On 2015-05-18 14:48, Anuj Wadehra wrote:
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 detailed Branching strategy followed by
Cassandra?
3. How to say "that I am looking into a JIRA"? Should I just put a
patch when ready?
ThanksAnuj Wadehra
