[
https://issues.apache.org/jira/browse/CASSANDRA-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680619#comment-17680619
]
Michael Semb Wever commented on CASSANDRA-18196:
------------------------------------------------
[~maedhroz], is there anything about what will be merged to trunk that breaks
upgrade compatibility against 3.x versions? If not, fixVersion should be 4.x.
If so, it needs to be expressed, fixVersion 5.x is appropriate and it should be
a blocker to CASSANDRA-17973.
> Initial Merge of Accord Feature Branch to Trunk
> -----------------------------------------------
>
> Key: CASSANDRA-18196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18196
> Project: Cassandra
> Issue Type: Task
> Components: Accord
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: High
> Fix For: 5.x
>
>
> Once we've resolved our feature flags situation (see CASSANDRA-18195) and
> in-flight work (see CASSANDRA-18192) we want before merge, here is the rough
> plan for getting {{cep-15-accord}} merged to {{trunk}}:
> 1.) Run cep-15-accord pre-squash against CircleCI to establish a baseline.
> 2.) Squash ninja commits out of cep-15-accord and rerun tests pre-rebase.
> 2.) Rebase cep-15-accord to trunk and rerun tests.
> 4.) Merge cep-15-accord to trunk if tests are clean and there are no public
> objections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
