Fix Versions in Jira

2015-12-16 Thread Josh McKenzie 
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, please tag those tickets as 2.1.X and 2.2.X respectively. Please
add 3.0.X and 3.X if the fix also applies to the 3.0+ releases.

If you have a ticket that's a new feature or improvement (3.EVEN) please
target as 3.X.

For bugfixes that are for 3.0+: most will be appropriate in 3.0.X and 3.X.
The only exception: if you're introducing a bugfix for a new feature added
in tick-tock (3.2, 3.4, 3.6, etc) that should be marked 3.X only.

Upon committing a ticket, committers please update the fixversion to
reflect the release(s) that ticket will be in (the listed unreleased
versions for each branch in JIRA at time of commit).

Let me know if you have any questions, and thanks!

~Josh

Re: Request for Wiki Edit Access

2015-12-16 Thread Jim Witschey 
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,
>
> Jim
>

Re: Request for Wiki Edit Access

2015-12-16 Thread Brandon Williams 
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
>

Request for Wiki Edit Access

2015-12-16 Thread Jim Witschey 
Could someone please give me edit access to the Apache wiki? Thanks,

Jim

[GitHub] cassandra pull request: CASSANDRA-9556: Add newer data types to ca...

2015-12-16 Thread jasonstack 
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-9556: Add newer data types to ca...

2015-12-16 Thread blerer 
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 request?



---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cassandra pull request: CASSANDRA-9556: Add newer data types to ca...

2015-12-16 Thread mshuler 
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/HowToContribute


---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---