|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "The next CloudStack release is 24" |
| 4 | +tags: [announcement] |
| 5 | +authors: [wido] |
| 6 | +slug: next-release-is-24 |
| 7 | +--- |
| 8 | + |
| 9 | +The Apache CloudStack project is changing how it numbers releases. The release |
| 10 | +that would have been 4.24 will be released as 24. The "4." prefix is gone. |
| 11 | + |
| 12 | +<!-- truncate --> |
| 13 | + |
| 14 | +## What changes |
| 15 | + |
| 16 | +· The next feature release is 24, with the full version 24.0.0 |
| 17 | + |
| 18 | +· Maintenance releases on that branch become 24.1.0, 24.2.0, and so on |
| 19 | + |
| 20 | +· Feature releases after that become 25, 26, 27 |
| 21 | + |
| 22 | +· The branch is called 24, packages and tarballs will say 24.0.0 |
| 23 | + |
| 24 | +## What does not change |
| 25 | + |
| 26 | +· 4.23 is not affected. It was released as planned under the old scheme |
| 27 | + |
| 28 | +· The release cadence stays the same |
| 29 | + |
| 30 | +· The LTS policy stays the same |
| 31 | + |
| 32 | +· The branching and release process stays the same |
| 33 | + |
| 34 | +· The backwards compatibility guarantees stay the same |
| 35 | + |
| 36 | +Dropping the "4." is not a signal that 24 breaks APIs or brings disruptive |
| 37 | +changes. It is a naming change and nothing else. |
| 38 | + |
| 39 | +## Why |
| 40 | + |
| 41 | +The leading "4." has not meant anything for years. We have not had a 5.0, and |
| 42 | +there was never a plan for one. In practice everybody already talks about "4.20" |
| 43 | +as twenty, and about "4.22" as twenty two. The docs, the branch names, the |
| 44 | +release notes and the mailing list all work that way. |
| 45 | + |
| 46 | +So the version we publish now matches the version people actually use. It also |
| 47 | +removes a question that kept coming back, which is what a major version bump |
| 48 | +would even mean for CloudStack. |
| 49 | + |
| 50 | +## What you may need to check |
| 51 | + |
| 52 | +· If you have tooling, scripts or monitoring that parses the CloudStack version |
| 53 | + and assumes it starts with "4.", update it. A version can now be three |
| 54 | + numbers, such as 24.0.0 |
| 55 | + |
| 56 | +· Repository paths and package names will use 24.x once 24.0.0 is out |
| 57 | + |
| 58 | +· The upgrade path itself is unchanged. Upgrading from 4.23 to 24 works the same |
| 59 | + way any other upgrade does |
| 60 | + |
| 61 | +## How this was decided |
| 62 | + |
| 63 | +This was a vote on the dev@cloudstack.apache.org mailing list. It opened on 14 |
| 64 | +August 2026, closed on 21 August 2026, and passed by lazy majority with four |
| 65 | +binding votes in favour, one non binding vote in favour, one abstention and one |
| 66 | +against. |
| 67 | + |
| 68 | +You can read the full thread here: |
| 69 | +[VOTE Version naming: drop the "4." prefix starting with release 24](http://www.mail-archive.com/dev@cloudstack.apache.org/msg107393.html) |
| 70 | + |
| 71 | +The version change has been made on the main branch. We will also talk about it |
| 72 | +at the CloudStack Collaboration Conference in November, so there is a chance to |
| 73 | +ask questions in person. |
| 74 | + |
| 75 | +If anything is unclear, ask on the users or dev mailing list. We would rather |
| 76 | +answer it now than have people confused about which release they are running. |
0 commit comments