Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 3 Nov 2016 15:40:59 +0000 (UTC)
From: "Joshua McKenzie (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13007871.1474971001000.174710.1478187659091@Atlassian.JIRA>
In-Reply-To: <JIRA.13007871.1474971001000@Atlassian.JIRA>
References: <JIRA.13007871.1474971001000@Atlassian.JIRA> <JIRA.13007871.1474971001600@arcas>
Subject: [jira] [Updated] (CASSANDRA-12716) Remove pre-3.0 compatibility
 code for 4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 03 Nov 2016 15:41:06 -0000


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

Joshua McKenzie updated CASSANDRA-12716:
----------------------------------------
    Reviewer: Aleksey Yeschenko

> Remove pre-3.0 compatibility code for 4.0
> -----------------------------------------
>
>                 Key: CASSANDRA-12716
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12716
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 4.0
>
>
> CASSANDRA-8099 make subsequent changes to internal formats so that we have quite a bit of backward compatibility code a bit over the place. Due to that, but also as a natural evolution, I believe we always had a tacit agreement that 3.0/3.X would be a mandatory step on the upgrade to 4.X, so that we can remove pre-3.0 compatibility (that is, we won't support going from any 2.x release directly to 4.0, you'll have to upgrade to at least some 3.0 release first).
> I think it's time to create the 4.0 branch and remove that pre-3.0 backward compatibility code, which should clean code quite a bit, and that's the goal of this issue.


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