Skip to content

Add a quote to the version 24 announcement and fix its Markdown lists #456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wido merged 2 commits into from
Sep 3, 2026
+20 −21
Merged

Add a quote to the version 24 announcement and fix its Markdown lists #456

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c9c3aa8
Add quote to the version 24 announcement blog post
wido Sep 3, 2026
14b056c
Use Markdown lists in the version 24 announcement blog post
wido Sep 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 20 additions & 21 deletions blog/2026-09-03-next-release-is-24/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,25 +13,18 @@ that would have been 4.24 will be released as 24. The "4." prefix is gone.

## What changes

· The next feature release is 24, with the full version 24.0.0

· Maintenance releases on that branch become 24.1.0, 24.2.0, and so on

· Feature releases after that become 25, 26, 27

· The branch is called 24, packages and tarballs will say 24.0.0
- The next feature release is 24, with the full version 24.0.0
- Maintenance releases on that branch become 24.1.0, 24.2.0, and so on
- Feature releases after that become 25, 26, 27
- The branch is called 24, packages and tarballs will say 24.0.0

## What does not change

· 4.23 is not affected. It was released as planned under the old scheme

· The release cadence stays the same

· The LTS policy stays the same

· The branching and release process stays the same

· The backwards compatibility guarantees stay the same
- 4.23 is not affected. It was released as planned under the old scheme
- The release cadence stays the same
- The LTS policy stays the same
- The branching and release process stays the same
- The backwards compatibility guarantees stay the same

Dropping the "4." is not a signal that 24 breaks APIs or brings disruptive
changes. It is a naming change and nothing else.
Expand All @@ -47,15 +40,21 @@ So the version we publish now matches the version people actually use. It also
removes a question that kept coming back, which is what a major version bump
would even mean for CloudStack.

>“We dropped the "4." because it stopped meaning anything years ago, not
>because anything changed. CloudStack is a mature platform, this change signals
>that. It has been running production clouds for more than 10 years and has
>been an Apache Software Foundation project since 2013. It just works. That
>stability is not a vendor promise, it is how the project is governed.”
>
>-Wido den Hollander, PMC Member, Apache CloudStack

## What you may need to check

· If you have tooling, scripts or monitoring that parses the CloudStack version
- If you have tooling, scripts or monitoring that parses the CloudStack version
and assumes it starts with "4.", update it. A version can now be three
numbers, such as 24.0.0

· Repository paths and package names will use 24.x once 24.0.0 is out

· The upgrade path itself is unchanged. Upgrading from 4.23 to 24 works the same
- Repository paths and package names will use 24.x once 24.0.0 is out
- The upgrade path itself is unchanged. Upgrading from 4.23 to 24 works the same
way any other upgrade does

## How this was decided
Expand Down
Loading