[jira] [Commented] (CASSANDRA-18196) Initial Merge of Accord Feature Branch to Trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682217#comment-17682217
]
Caleb Rackliffe commented on CASSANDRA-18196:
-
[~mck] Yup. (I was going to handle {{accord_demo.txt}} in CASSANDRA-18107, but
we can do it here instead.)
> 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: 4.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
[jira] [Commented] (CASSANDRA-18196) Initial Merge of Accord Feature Branch to Trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681719#comment-17681719
]
Michael Semb Wever commented on CASSANDRA-18196:
Small very trivial thing (can be separate ticket, idc):
Can the files accord_demo.txt and simulator.sh not be top-level please. the
latter can go into .build/ where other build scripts are (coming).
> 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: 4.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
[jira] [Commented] (CASSANDRA-18196) Initial Merge of Accord Feature Branch to Trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17680710#comment-17680710
]
Benedict Elliott Smith commented on CASSANDRA-18196:
No, there is not. But, I do not believe this would determine the fix version
anyway.
> 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: 4.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
[jira] [Commented] (CASSANDRA-18196) Initial Merge of Accord Feature Branch to Trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17680704#comment-17680704
]
Caleb Rackliffe commented on CASSANDRA-18196:
-
[~mck] I don't think we have, but I'll double check w/ [~benedict].
> 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: 4.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
[jira] [Commented] (CASSANDRA-18196) Initial Merge of Accord Feature Branch to Trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
