[
https://issues.apache.org/jira/browse/CASSANDRA-10488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953135#comment-14953135
]
Sylvain Lebresne commented on CASSANDRA-10488:
----------------------------------------------
bq. There might have been other forward-compatibility changes in 2.1 or 2.2
that I missed in later releases.
I can't remember anything so I've simply push a commit going with 2.1.9+ and
2.2.1+. If someone remember a reason why that's incorrect, please speak. I'm
gonna mark that issue as testing as we should check that our upgrading test do
at least pass for those versions, but since that's really pending the
completion of CASSANDRA-10166.
> Document supported upgrade paths to 3.0 in NEWS.txt
> ---------------------------------------------------
>
> Key: CASSANDRA-10488
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10488
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation & website
> Reporter: Tyler Hobbs
> Assignee: Sylvain Lebresne
> Priority: Blocker
> Fix For: 3.0.0 rc2
>
>
> Due to CASSANDRA-9849, we only support upgrading to 3.0 from 2.1.9+ or
> 2.2.1+. This needs to be documented in the "Upgrading" section of NEWS.txt.
> (There might have been other forward-compatibility changes in 2.1 or 2.2 that
> I missed in later releases.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
