With some of the recent changes to our release structure and versioning,
we're seeing some confusion concerning the appropriate fixversion for
tickets in JIRA. Hopefully the following will help clear things up a bit.
If you have a ticket that's reproduced in and is a bugfix for the 2.1 or
2.2 line
I have added you.
On Wed, Dec 16, 2015 at 11:55 AM, Jim Witschey
wrote:
> Could someone please give me edit access to the Apache wiki? Thanks,
>
> Jim
>
For what it's worth, my username is 'Jim Witschey' (I do not know why this
is a legal usename) and I'm registered with this email address (
jim.witsc...@datastax.com).
On Wed, Dec 16, 2015 at 12:55 PM Jim Witschey
wrote:
> Could someone please give me edit access to the Apache wiki? Thanks,
>
>
Could someone please give me edit access to the Apache wiki? Thanks,
Jim
Github user mshuler commented on the pull request:
https://github.com/apache/cassandra/pull/58#issuecomment-165142570
The Cassandra JIRA is public, so for future reference, public patches
posted to a public JIRA should probably suffice :)
http://wiki.apache.org/cassandra/HowToContr
Github user jasonstack commented on the pull request:
https://github.com/apache/cassandra/pull/58#issuecomment-165127521
Thank you. I know here is a mirror, but my company policy requires to make
public PR.. sorry for the trouble.
---
If your project is set up for it, you can reply t
Github user jasonstack closed the pull request at:
https://github.com/apache/cassandra/pull/58
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
Github user blerer commented on the pull request:
https://github.com/apache/cassandra/pull/58#issuecomment-165125795
We cannot merge the PR because this repository is only a mirror from:
git://git.apache.org/cassandra.git
I have committed your patch. Could you close your pull requ