Updating version numbers for release 24.0.0-SNAPSHOT

[wido]

Description

Following the [VOTE] "Version naming: drop the "4." prefix starting with release 24" on dev@cloudstack.apache.org, started on 14 August 2026 and closed on 21 August 2026 at 12:00 UTC, the release that would have been 4.24 is released as 24, i.e. 24.0.0. Subsequent feature releases become 25, 26, and so on, and maintenance releases on the 24 branch become 24.1.0, 24.2.0, and so on.

The vote passed by lazy majority with 4 binding +1 votes (Wido den Hollander, Daan Hoogland, Kiran Chavala, Vishesh Jindal), 1 non-binding +1 (Simon Weller), 1 +0 (Abhishek) and 1 -1 (Joao Jandre Paraquetti).

This changes the version only, touching the same files that tools/build/setnextversion.sh does:

• in all pom.xml files
• debian/changelog
• tools/marvin/setup.py
• tools/docker/Dockerfile, Dockerfile.marvin and Dockerfile.s390x

The leading "4." has not carried any meaning for many years. Dropping it does not affect the release cadence, the LTS policy, the branching and release process or the backwards-compatibility guarantees, and it is not a signal that 24 breaks APIs or introduces disruptive changes.

org.apache.cloudstack.utils.CloudStackVersion already parses and compares both three and four position versions, normalising 24.0.0 to 24.0.0.0, so 24.0.0 still compares greater than 4.23.0.0.

Vote thread:
http://www.mail-archive.com/dev@cloudstack.apache.org/msg107393.html

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

Local builds have been run, all compiles

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 19.78%. Comparing base (b7a834b) to head (d32d784).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main   #14041   +/-   ##
=========================================
  Coverage     19.78%   19.78%           
+ Complexity    19998    19996    -2     
=========================================
  Files          6371     6371           
  Lines        575899   575899           
  Branches      70495    70495           
=========================================
+ Hits         113967   113969    +2     
- Misses       449501   449505    +4     
+ Partials      12431    12425    -6     

Flag	Coverage Δ
uitests	3.53% <ø> (ø)
unittests	21.06% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[DaanHoogland]

clgtm

[nvazquez]

Thanks @wido - largely looks good. Just a question, are we keeping the schema upgrade SQL path files named as before or those should also be updated?

[Pearl1594]

Most changes have been taken care of.
Just wondering if we also need to look at the ci workflow here: https://github.com/apache/cloudstack/blob/main/.github/workflows/docker-cloudstack-simulator.yml#L24-L26 - it only triggers the docker image build on tags matching 4.* / 5.*, so once we start tagging releases as 24.0.0 etc, this workflow won't pick it up and the image build would just silently not run.

Also, since we've been following the 4.x naming for several years, its pretty likely contributors may keep writing since = "4.24.0" out of muscle memory despite this being communicated. Do you think it makes sense / would help to add a pre-commit hook to catch that automatically instead of relying on reviewers to spot it every time? This could be done on a separate PR too - we could add the hook to .pre-commit-config.yaml

[wido]

Thanks @wido - largely looks good. Just a question, are we keeping the schema upgrade SQL path files named as before or those should also be updated?

Good one. I only did a search and replace, but these files need to be renamed indeed. Let me check that and push a new commit if needed

Most changes have been taken care of. Just wondering if we also need to look at the ci workflow here: https://github.com/apache/cloudstack/blob/main/.github/workflows/docker-cloudstack-simulator.yml#L24-L26 - it only triggers the docker image build on tags matching 4.* / 5.*, so once we start tagging releases as 24.0.0 etc, this workflow won't pick it up and the image build would just silently not run.

Also, since we've been following the 4.x naming for several years, its pretty likely contributors may keep writing since = "4.24.0" out of muscle memory despite this being communicated. Do you think it makes sense / would help to add a pre-commit hook to catch that automatically instead of relying on reviewers to spot it every time? This could be done on a separate PR too - we could add the hook to .pre-commit-config.yaml

That pre-commit hook looks good, can you make a PR for this? I'm not really a big commit hook genius :-)

[Pearl1594]

Thanks @wido - largely looks good. Just a question, are we keeping the schema upgrade SQL path files named as before or those should also be updated?

Good one. I only did a search and replace, but these files need to be renamed indeed. Let me check that and push a new commit if needed

Most changes have been taken care of. Just wondering if we also need to look at the ci workflow here: https://github.com/apache/cloudstack/blob/main/.github/workflows/docker-cloudstack-simulator.yml#L24-L26 - it only triggers the docker image build on tags matching 4.* / 5.*, so once we start tagging releases as 24.0.0 etc, this workflow won't pick it up and the image build would just silently not run.
Also, since we've been following the 4.x naming for several years, its pretty likely contributors may keep writing since = "4.24.0" out of muscle memory despite this being communicated. Do you think it makes sense / would help to add a pre-commit hook to catch that automatically instead of relying on reviewers to spot it every time? This could be done on a separate PR too - we could add the hook to .pre-commit-config.yaml

That pre-commit hook looks good, can you make a PR for this? I'm not really a big commit hook genius :-)

Sure, can do it once this PR gets merged.

[blueorangutan]

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 19073

[weizhouapache]

@blueorangutan test

[blueorangutan]

@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[weizhouapache]

@blueorangutan package

[weizhouapache]

@blueorangutan package

[blueorangutan]

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 19100

[weizhouapache]

@blueorangutan test matrix

[blueorangutan]

@weizhouapache a [SL] Trillian-Jenkins matrix job (ol8 mgmt + kvm-ol8, ubuntu22 mgmt + kvm-ubuntu22, ol8 mgmt + vmware-70u3, ol9 mgmt + xcpng82) has been kicked to run smoke tests

[blueorangutan]

[SF] Trillian test result (tid-16902)
Environment: kvm-ol8 (x2), zone: Advanced Networking with Mgmt server ol8
Total time taken: 59208 seconds
Marvin logs: [archive removed]
Smoke tests completed. 156 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test	Result	Time (s)	Test File

[blueorangutan]

[SF] Trillian test result (tid-16904)
Environment: vmware-70u3 (x2), zone: Advanced Networking with Mgmt server ol8
Total time taken: 70090 seconds
Marvin logs: [archive removed]
Smoke tests completed. 152 look OK, 4 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test	Result	Time (s)	Test File
test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80	Error	644.73	test_internal_lb.py
test_02_internallb_roundrobin_1RVPC_3VM_HTTP_port80	Failure	803.42	test_internal_lb.py
test_12_deploy_vm_with_root_disk_encryption	Error	15.19	test_kms_lifecycle.py
test_05_list_volumes_isrecursive	Failure	0.07	test_list_volumes.py
test_07_list_volumes_listall	Failure	0.06	test_list_volumes.py
test_01_vpn_usage	Error	1.14	test_usage.py

[blueorangutan]

[SF] Trillian test result (tid-16905)
Environment: xcpng82 (x2), zone: Advanced Networking with Mgmt server ol9
Total time taken: 78264 seconds
Marvin logs: [archive removed]
Smoke tests completed. 147 look OK, 9 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test	Result	Time (s)	Test File
test_01_events_resource	Error	265.92	test_events_resource.py
test_12_deploy_vm_with_root_disk_encryption	Error	17.68	test_kms_lifecycle.py
test_09_vpc_source_nat_ip_update	Error	24.16	test_network_extension_namespace.py
test_01_non_strict_host_anti_affinity	Error	159.18	test_nonstrict_affinity_group.py
test_02_non_strict_host_affinity	Error	74.10	test_nonstrict_affinity_group.py
test_02_list_snapshots_with_removed_data_store	Error	14.12	test_snapshots.py
test_02_list_snapshots_with_removed_data_store	Error	14.12	test_snapshots.py
test_01_volume_usage	Failure	103.43	test_usage.py
test_01_vpn_usage	Error	1.13	test_usage.py
test_11_destroy_vm_and_volumes	Error	24.50	test_vm_life_cycle.py
test_01_migrate_vm_strict_tags_success	Error	53.83	test_vm_strict_host_tags.py
test_02_cancel_host_maintenace_with_migration_jobs	Error	0.63	test_host_maintenance.py
test_03_cancel_host_maintenace_with_migration_jobs_failure	Error	0.72	test_host_maintenance.py

[weizhouapache]

lgtm

[weizhouapache]

@nvazquez @RosiKyu
smoke tests look good. can we merge ?

[nvazquez]

Hi @weizhouapache @wido I think we are just missing upgrade testing, once we get that manually verified and approved it can be merged IMO

[wido]

Here we go, a install with version 24. Upgraded from 4.23:

root@man-138-d03-39:~# dpkg -l|grep cloudstack
ii  cloudstack-common                     24.0.0-SNAPSHOT~noble                            all          A common package which contains files which are shared by several CloudStack packages
ii  cloudstack-management                 24.0.0-SNAPSHOT~noble                            all          CloudStack server library
root@man-138-d03-39:~#

MariaDB [cloud]> select * from version;
+----+----------+---------------------+----------+
| id | version  | updated             | step     |
+----+----------+---------------------+----------+
|  1 | 4.0.0    | 2026-09-03 13:28:43 | Complete |
|  2 | 4.1.0    | 2026-09-03 13:30:30 | Complete |
|  3 | 4.2.0    | 2026-09-03 13:30:30 | Complete |
|  4 | 4.2.1    | 2026-09-03 13:30:30 | Complete |
|  5 | 4.3.0    | 2026-09-03 13:30:30 | Complete |
|  6 | 4.4.0    | 2026-09-03 13:30:31 | Complete |
|  7 | 4.4.1    | 2026-09-03 13:30:31 | Complete |
|  8 | 4.4.2    | 2026-09-03 13:30:31 | Complete |
|  9 | 4.5.0    | 2026-09-03 13:30:33 | Complete |
| 10 | 4.4.4    | 2026-09-03 13:30:33 | Complete |
| 11 | 4.5.1    | 2026-09-03 13:30:33 | Complete |
| 12 | 4.5.2    | 2026-09-03 13:30:33 | Complete |
| 13 | 4.5.3    | 2026-09-03 13:30:33 | Complete |
| 14 | 4.6.0    | 2026-09-03 13:30:33 | Complete |
| 15 | 4.6.1    | 2026-09-03 13:30:33 | Complete |
| 16 | 4.7.0    | 2026-09-03 13:30:33 | Complete |
| 17 | 4.7.1    | 2026-09-03 13:30:33 | Complete |
| 18 | 4.8.0    | 2026-09-03 13:30:33 | Complete |
| 19 | 4.8.1    | 2026-09-03 13:30:33 | Complete |
| 20 | 4.9.0    | 2026-09-03 13:30:34 | Complete |
| 21 | 4.9.1.0  | 2026-09-03 13:30:34 | Complete |
| 22 | 4.9.2.0  | 2026-09-03 13:30:34 | Complete |
| 23 | 4.9.3.0  | 2026-09-03 13:30:34 | Complete |
| 24 | 4.10.0.0 | 2026-09-03 13:30:34 | Complete |
| 25 | 4.11.0.0 | 2026-09-03 13:30:34 | Complete |
| 26 | 4.11.1.0 | 2026-09-03 13:30:34 | Complete |
| 27 | 4.11.2.0 | 2026-09-03 13:30:34 | Complete |
| 28 | 4.11.3.0 | 2026-09-03 13:30:34 | Complete |
| 29 | 4.12.0.0 | 2026-09-03 13:30:34 | Complete |
| 30 | 4.13.0.0 | 2026-09-03 13:30:34 | Complete |
| 31 | 4.13.1.0 | 2026-09-03 13:30:34 | Complete |
| 32 | 4.14.0.0 | 2026-09-03 13:30:35 | Complete |
| 33 | 4.15.0.0 | 2026-09-03 13:30:35 | Complete |
| 34 | 4.15.1.0 | 2026-09-03 13:30:35 | Complete |
| 35 | 4.15.2.0 | 2026-09-03 13:30:35 | Complete |
| 36 | 4.16.0.0 | 2026-09-03 13:30:35 | Complete |
| 37 | 4.16.1.0 | 2026-09-03 13:30:35 | Complete |
| 38 | 4.17.0.0 | 2026-09-03 13:30:35 | Complete |
| 39 | 4.17.1.0 | 2026-09-03 13:30:35 | Complete |
| 40 | 4.17.2.0 | 2026-09-03 13:30:35 | Complete |
| 41 | 4.18.0.0 | 2026-09-03 13:30:36 | Complete |
| 42 | 4.18.1.0 | 2026-09-03 13:30:37 | Complete |
| 43 | 4.19.0.0 | 2026-09-03 13:30:37 | Complete |
| 44 | 4.19.1.0 | 2026-09-03 13:30:37 | Complete |
| 45 | 4.20.0.0 | 2026-09-03 13:30:37 | Complete |
| 46 | 4.20.1.0 | 2026-09-03 13:30:38 | Complete |
| 47 | 4.20.3.0 | 2026-09-03 13:30:38 | Complete |
| 48 | 4.20.4.0 | 2026-09-03 13:30:38 | Complete |
| 49 | 4.21.0.0 | 2026-09-03 13:30:38 | Complete |
| 50 | 4.22.0.0 | 2026-09-03 13:30:38 | Complete |
| 51 | 4.22.1.0 | 2026-09-03 13:30:38 | Complete |
| 52 | 4.23.0.0 | 2026-09-03 13:30:38 | Complete |
| 53 | 24.0.0   | 2026-09-05 20:47:23 | Complete |
+----+----------+---------------------+----------+
53 rows in set (0.000 sec)

MariaDB [cloud]>

As you can see, version 24 was installed and upgrade went fine. I was able to log on to the UI.

[DaanHoogland]

Do we need more testing @RosiKyu @nvazquez . As this will probably need “some” rebasing of PRs Ir would be good if we can merge it now.