Updating version numbers for release 24.0.0-SNAPSHOT by wido · Pull Request #14041 · apache/cloudstack

wido · 2026-09-02T15:32:12Z

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

Screenshots (if appropriate):

How Has This Been Tested?

Local builds have been run, all compiles

codecov · 2026-09-02T15:42:03Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 19.78%. Comparing base (b7a834b) to head (d32d784).

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #14041      +/-   ##
============================================
- Coverage     19.78%   19.78%   -0.01%     
+ Complexity    19998    19994       -4     
============================================
  Files          6371     6371              
  Lines        575899   575899              
  Branches      70495    70495              
============================================
- Hits         113967   113942      -25     
- Misses       449501   449531      +30     
+ Partials      12431    12426       -5

Flag	Coverage Δ
uitests	`3.53% <ø> (ø)`
unittests	`21.05% <ø> (-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

DaanHoogland · 2026-09-02T18:13:39Z

@blueorangutan package

blueorangutan · 2026-09-02T18:16:05Z

@DaanHoogland 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 · 2026-09-02T18:28:49Z

Packaging result [SF]: ✖️ el8 ✖️ el9 ✖️ debian ✖️ suse15. SL-JID 19069

wido · 2026-09-02T18:51:17Z

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 :-)

@nvazquez

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: * <version> in all pom.xml files * debian/changelog * tools/marvin/setup.py * tools/docker/Dockerfile, Dockerfile.marvin and Dockerfile.s390x Two places additionally assumed the version string starts with a single digit followed by a dot, which no longer holds now that the version is 24.0.0-SNAPSHOT instead of 4.24.0.0-SNAPSHOT, and are fixed here as well: * packaging/package.sh picked the version out of the maven-help-plugin output with 'grep ^[0-9]\.', which does not match 24.0.0-SNAPSHOT. That left VERSION empty and failed the el8, el9, debian and suse15 packaging jobs. It now uses 'grep -E ^[0-9]+\.'. * the docker-cloudstack-simulator workflow only triggered on tags matching 4.* and 5.*, so a 24.0.0 tag would silently not build an image. Those patterns are replaced by a single '[0-9]+.[0-9]+.*' which matches any numeric release tag under either naming scheme. Reported by @nvazquez. 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 Signed-off-by: Wido den Hollander <wido@widodh.nl>

weizhouapache · 2026-09-02T19:44:18Z

@blueorangutan package

weizhouapache · 2026-09-02T19:44:35Z

we may need Trillian changes too

Pearl1594 · 2026-09-02T20:10:14Z

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 · 2026-09-02T21:24:00Z

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

wido requested review from DaanHoogland and weizhouapache September 2, 2026 15:32

wido requested review from Pearl1594, nvazquez, rp- and slavkap as code owners September 2, 2026 15:32

DaanHoogland approved these changes Sep 2, 2026

View reviewed changes

nvazquez reviewed Sep 2, 2026

View reviewed changes

Pearl1594 reviewed Sep 2, 2026

View reviewed changes

resmo reviewed Sep 2, 2026

View reviewed changes

Comment thread .github/workflows/docker-cloudstack-simulator.yml Outdated

wido force-pushed the v24 branch from 8a4b6d2 to b43abb8 Compare September 2, 2026 19:22

wido force-pushed the v24 branch from b43abb8 to d32d784 Compare September 2, 2026 19:29

Navigation Menu

Uh oh!

Updating version numbers for release 24.0.0-SNAPSHOT - #14041

Updating version numbers for release 24.0.0-SNAPSHOT#14041
wido wants to merge 1 commit into
apache:mainfrom
wido:v24

wido commented Sep 2, 2026

Uh oh!

codecov Bot commented Sep 2, 2026 •

edited

Loading

Uh oh!

DaanHoogland left a comment

Uh oh!

nvazquez left a comment

Uh oh!

Pearl1594 left a comment

Uh oh!

DaanHoogland commented Sep 2, 2026

Uh oh!

blueorangutan commented Sep 2, 2026

Uh oh!

blueorangutan commented Sep 2, 2026

Uh oh!

wido commented Sep 2, 2026

Uh oh!

Uh oh!

weizhouapache commented Sep 2, 2026

Uh oh!

weizhouapache commented Sep 2, 2026

Uh oh!

Pearl1594 commented Sep 2, 2026

Uh oh!

blueorangutan commented Sep 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

Uh oh!

Conversation

wido commented Sep 2, 2026

Description

Types of changes

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

Bug Severity

Screenshots (if appropriate):

How Has This Been Tested?

Uh oh!

codecov Bot commented Sep 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

DaanHoogland left a comment

Choose a reason for hiding this comment

Uh oh!

nvazquez left a comment

Choose a reason for hiding this comment

Uh oh!

Pearl1594 left a comment

Choose a reason for hiding this comment

Uh oh!

DaanHoogland commented Sep 2, 2026

Uh oh!

blueorangutan commented Sep 2, 2026

Uh oh!

blueorangutan commented Sep 2, 2026

Uh oh!

wido commented Sep 2, 2026

Uh oh!

Uh oh!

weizhouapache commented Sep 2, 2026

Uh oh!

weizhouapache commented Sep 2, 2026

Uh oh!

Pearl1594 commented Sep 2, 2026

Uh oh!

blueorangutan commented Sep 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

codecov Bot commented Sep 2, 2026 •

edited

Loading