[ 
https://issues.apache.org/jira/browse/CASSANDRA-17973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680756#comment-17680756
 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-17973 at 1/25/23 7:09 PM:
--------------------------------------------------------------------------

{quote}Because there are so many repositories and build/test components 
involved, to untangle the introduction of jdk17, we're looking at temporarily 
introducing jdk17 (CASSANDRA-18179) then completing jdk17 support and then 
removing jdk8.
{quote}
Just to clarify, we do not plan to introduce it in CI (J8+J11+J17). There is 
ongoing discussion to enable trunk to compile and test J17 when people want and 
when everything is ready to close CASSANDRA-16895, we will switch from J8+J11 
to J11+J17 in CI. Feature branch to enable people to test was considered but it 
will make it more complicated. More info will be shared broadly soon, this 
strategy is fresh idea


was (Author: e.dimitrova):
{quote}Because there are so many repositories and build/test components 
involved, to untangle the introduction of jdk17, we're looking at temporarily 
introducing jdk17 (CASSANDRA-18179) then completing jdk17 support and then 
removing jdk8.
{quote}
Just to clarify, we do not plan to introduce it in CI (J8+J11+J17). There is 
ongoing discussion to enable trunk to compile and test J17 when people want and 
when everything is ready to close CASSANDRA-16895, we will switch from J8+J11 
to J11+J17 in CI. Feature branch to enable people to test was considered but it 
will make it more complicated. More info will be shared broadly soon. 

> Change trunk 4.2 to 5.0
> -----------------------
>
>                 Key: CASSANDRA-17973
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17973
>             Project: Cassandra
>          Issue Type: Task
>          Components: Build
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 5.x
>
>
> 1. Bump trunk's version 
> {code}
> git switch trunk
> # increment version to 5.0
> edit build.xml debian/changelog CHANGES.txt NEWS.txt README.asc
> {code}
> 2. Update jvm-dtest supported upgrade paths
>  - 
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>  
> 3. Update `4.2` to jira versions
> Change `4.2` to `5.0`
> Change `4.x` to `5.x`
> 4. Update docker images to include cassandra-5.0
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
>  - 
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
>  - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
>  - 
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to