Hi all, The key features, improvements, critical fixes, and other planned updates for 4.22 are now in place. The current health of main branch also looks good.
I’m currently in the process of preparing the packages and system VM templates. Please expect the first Release Cut either today or early next week. Looking forward to your validations and feedback on the RC. Regards, Harikrishna From: Harikrishna Patnala <[email protected]> Date: Tuesday, 14 October 2025 at 9:16 AM To: [email protected] <[email protected]> Cc: users <[email protected]> Subject: Re: 4.22.0 Release plan Hi, There is a critical issue reported in main with CKS and VMware 8 https://github.com/apache/cloudstack/issues/11831 and we are currently addressing with system VM template change. Once this is addressed and have good healthy main branch, we will be cutting our 1st RC in this week. I’ll keep you posted on that. Thanks for all the help on the issues and PRs. Regards, Harikrishna From: Rohit Yadav <[email protected]> Date: Wednesday, 8 October 2025 at 11:36 AM To: [email protected] <[email protected]> Cc: users <[email protected]> Subject: Re: 4.22.0 Release plan I like the Hari's approach, it could help to align major releases to be more timely next year and allow us to aim for the next regular 4.23 in Q2 and 4.24 LTS in Q3/Q4 next year. If we push 4.22 by 16 weeks, we'll have no new major LTS release this year. Fwiw, if we can target 4.23 in Q2 2026 (i.e. freeze by late Q1 or early Q2), considering people tend to take time off in Dec-Jan, we'll easily have 16 weeks or more for the dev community to target new features with 4.23. Regards. ________________________________ From: Harikrishna Patnala <[email protected]> Sent: Wednesday, October 8, 2025 10:35 To: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: 4.22.0 Release plan Hi Bernardo, Thanks for sharing your thoughts, I understand your concern about having enough time between major releases. As I mentioned in my earlier notes, the proposed timeline was planned with past delays and upcoming events in mind. Since 4.22 is an LTS release, the primary focus is on stability and consolidation. In 4.22 also includes a good number of new features and improvements, many of which are already merged or in the pipeline. In parallel, with 4.20.2 progressing, many of the fixes and improvements are also being merged into 4.22, further contributing to its stability. Starting the freeze earlier gives us a realistic buffer to complete the release within this year while ensuring a reliable LTS version and helps future releases. Anyways, now we can keep these dates flexible if any important items need to be fitted into the release. Thanks, Harikrishna From: Bernardo De Marco Gonçalves <[email protected]> Date: Saturday, 4 October 2025 at 12:03 AM To: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: 4.22.0 Release plan Hello, all Don't you guys think it might be too early to freeze the main branch and cut the first RC for the 4.22 release? At the moment, we have 43 merged and 97 open PRs targeting 4.22. I haven’t gone through all of them, but IMHO, we should aim for more impactful features to justify the release of a new "major". Besides that, considering that 4.21 was released on August 29th, how are developers supposed to systematically develop substantial new features in a gap of just one month? It seems very unlikely for me. And, wouldn’t this risk making 4.22 feel more like a 4.21 "minor" update for end users? Thus, I believe we should have an interval of at least 16 weeks until we consider freezing the main branch. This would also help to maintain a more consistent interval between ACS "majors". What do you guys think about that? Best regards, Bernardo De Marco Gonçalves (bernardodemarco) Em sex., 3 de out. de 2025 às 07:54, Harikrishna Patnala < [email protected]> escreveu: > Hi all, > > As a follow-up to my earlier note, I’d like to call the freeze date for > 4.22 as October 10th. > We can then plan to cut the first RC in the week following October 10th, > after we’ve had some time to stabilize the branch. > > Please let me know if there are any PRs or issues that need attention to > be included in 4.22 before the freeze, we can plan accordingly. > > Thanks, > Harikrishna > > > > > From: Harikrishna Patnala <[email protected]> > Date: Monday, 25 August 2025 at 11:41 AM > To: [email protected] <[email protected]>, > [email protected] <[email protected]> > Subject: Re: 4.22.0 Release plan > Hi Joao, > > Thanks for reviewing the dates. Ideally, I agree that November or December > would be better, but realistically I see a few concerns as November month > has the CloudStack Collaboration Conference, when many community members > will be busy with preparations and travel. December month brings Christmas > and New Year holidays, which may reduce the support we can count on. > > Also, looking at the history of our release date announcements versus > actual releases, there have often been delays. I proposed the current plan > with that in mind, aiming for a safer timeline to ensure we can complete > the release this year. > > Regards, > Harikrishna > > From: João Jandre Paraquetti <[email protected]> > Date: Friday, 22 August 2025 at 5:28 PM > To: [email protected] <[email protected]> > Subject: Re: 4.22.0 Release plan > Hello, all > > Considering that we have yet to release 4.21, wanting to cut the first > 4.22 RC in early October (less than 2 months from now) seems a bit > early. Considering our usual release cadence, I think that maybe late > November or early December would be better. > > Best regards, > > João > > On 8/22/25 00:44, Harikrishna Patnala wrote: > > Hi all, > > > > As the ongoing 4.21 release is coming to an end, I would like to propose > the plan for our next LTS release, 4.22.0. > > > > As discussed here [1], I propose the following timelines to ensure the > release stays on track for this year: > > > > * Feature/Improvement/Bug-fix Freeze: End of September. > > * First Release Candidate (RC) cut: Early October. > > > > We have the project board for 4.22.0 milestone[2] here [3], where I have > already moved all existing issues and PRs to this release. Please plan your > features, improvements, and bug fixes accordingly, and aim to get them > merged before the freeze date. > > > > If you have any items to include, please feel free to ping me > (@harikrishna-patnala). > > Let me know if you have any questions or feedback. > > > > > > [1] https://lists.apache.org/thread/0y4822lytf57llzqhr6qq8otdr13bbg9 > > > > [2] https://github.com/apache/cloudstack/milestone/37 > > > > [3] https://github.com/orgs/apache/projects/523/views/2 > > > > Regards, > > Harikrishna > > > > > > > > >
