Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 13 Aug 2015 23:14:48 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12850062.1438201591000.61866.1439507688355@Atlassian.JIRA>
In-Reply-To: <JIRA.12850062.1438201591000@Atlassian.JIRA>
References: <JIRA.12850062.1438201591000@Atlassian.JIRA>
 <JIRA.12850062.1438201591381@arcas>
Subject: [jira] [Updated] (CASSANDRA-9930) Add test coverage for 2.1 -> 3.0
 upgrades
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-9930:
--------------------------------------
    Issue Type: Test  (was: New Feature)

> 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
>             Fix For: 3.0.0 rc1
>
>
> 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)