You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/11/05 18:05:27 UTC

[jira] [Commented] (CASSANDRA-9930) Add test coverage for 2.1 -> 3.0 upgrades

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

Aleksey Yeschenko commented on CASSANDRA-9930:
----------------------------------------------

[~rhatch] Can the issue be closed now?

> Add test coverage for 2.1 -> 3.0 upgrades
> -----------------------------------------
>
>                 Key: CASSANDRA-9930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9930
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ryan McGuire
>            Assignee: Andrew Hust
>             Fix For: 3.0.0
>
>
> Once we move to a [tick-tock model|http://www.mail-archive.com/dev%40cassandra.apache.org/msg07771.html] we will need the ability to upgrade from stable release to stable release, skipping a single version in the process.
> Example: 3.0 -> 3.2 (skipping the pass-through upgrade to 3.1 we normally have to do)
> I would recommend we code this so that we can upgrade 2.1 directly to 3.0 as well, it's probably too much work to do this for versions prior to that.



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