[ 
https://issues.apache.org/jira/browse/CASSANDRA-9352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540827#comment-14540827
 ] 

Sam Tunnicliffe commented on CASSANDRA-9352:
--------------------------------------------

Pushed a branch [here|https://github.com/beobal/cassandra/tree/9352-notest] 
with the changes. It includes a commit which updates the thrift interface file 
and includes a regenerated {{Cassandra.java}}. The only change there is in a 
comment, so it's not essential for anything functional. 

I've also pushed a dtest branch 
[here|https://github.com/beobal/cassandra-dtest/commits/9352] which switches 
most references to 3.0 to 2.2. I found a couple of {{@since('3.0')}} 
annotations which also have {{@requires}} on open tickets, whose versions are 
still at 3.x (e.g. {{user_types_test:TestUserTypes.udt_subfield_test}}, 
{{global_indexes_test}}, {{sstablelist_test}} and several in {{cql_tests}} 
relating to CASSANDRA-7396); I've left these as they are. Although 
CASSANDRA-9007 is still  open, I've modified the {{@since}} on 
{{validation.py}} as I guess it's part of our in progress testing improvements, 
so we might actually want that one to be runnable.  

Cassci is not going to pick this up for testing automatically. 
[~philipthompson] is on the case there, setting up a custom job to run the 
modified dtests

> Update all references to 3.0 for 2.2 release
> --------------------------------------------
>
>                 Key: CASSANDRA-9352
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9352
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 2.2 beta 1
>
>
> NEWS.txt, CHANGES.txt, code comments, constant names 
> ({{MessagingService.VERSION_30}}, {{CommitLogDescriptor.VERSION_30}}), etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to