Hmm, so does that mean my pending bugfix PRs for the 4.22 branch won't make it into 4.22.2.0?

These are all 100% bug fixes, not features, and we're running all in production ourselves.   Most have been open here for > 1 month and I did the requested pinging on the PRs for things that needed to make it into 4.22.2.0 when requested.

*Critical (Deadlocks, Resource Leaks, Unusable Basic Functionality)*

 * Serialize NIC add/remove on the target VM's work job queue (Fixes
   Redundant VRs!) https://github.com/apache/cloudstack/pull/14139
 * kvm: stop a stuck rbd_open from wedging the agent (fix agent
   deadlock with rbd!) https://github.com/apache/cloudstack/pull/14199
 * engine: do not orphan an instance on a forced power report during
   start (instance leak!) https://github.com/apache/cloudstack/pull/14207
 * engine: do not force the destroy stop while the host may reconnect
   (instance leak!) https://github.com/apache/cloudstack/pull/14233

*High (Similar to Critical, but workarounds may exist)*

 * DRS: honour anti-affinity when planning and executing migrations
   (without this, DRS makes anti-affinity void)
   https://github.com/apache/cloudstack/pull/14108
 * VPC ACL: apply every CIDR of a multi-CIDR rule, in order (fix for
   invalid ACL order): https://github.com/apache/cloudstack/pull/14350

*Medium (Though these are all about poorly generated FW rules, so could be rated higher)*

 * VPC ACL: keep the ports and ICMP type of rules given by protocol
   number or as upper-case ICMP
   https://github.com/apache/cloudstack/pull/14357
 * Validate ACL, firewall and routing rule protocols against the list,
   not as a substring https://github.com/apache/cloudstack/pull/14359
 * IPv6 ACL: match protocol-number rules with meta l4proto
   https://github.com/apache/cloudstack/pull/14360
 * VPC ACL: match all ports for a tcp/udp rule given without ports
   https://github.com/apache/cloudstack/pull/14364

*Low*

 * kvm: fix storage pool refcount race and false umount success
   https://github.com/apache/cloudstack/pull/14189

Thanks.

-Brad

On 10/26/26 7:20 AM, Vladimir Petrov wrote:
Hi all,

The planned items for 4.22.2 are now complete, so I would like to announce a code freeze on the 4.22 branch. Most of the open items in the 4.22.2 milestone [1] will be deferred to the next feasible milestone.

From now on, only critical/blocker fixes and stabilization fixes will be accepted. I'll work towards cutting 4.22.2.0 RC1, and start the voting
process.

Appreciate your support. Thanks.

  [1] https://github.com/apache/cloudstack/milestone/46

P.S.  PR #14383 is merged, as requested by Fabricio.

Regards,
Vladimir


<https://www.cloudstackcollab.org>
------------------------------------------------------------------------
*From:* Fabricio Duarte <[email protected]>
*Sent:* 23 October 2026 03:44
*To:* [email protected] <[email protected]>; [email protected] <[email protected]>
*Subject:* Re: 4.22.2 Release plan
Vladi, please also include PR #14383 in the release. It reverts a change
that inadvertently reduces the CPU quota of VMs using compute offerings
with CPU cap enabled once they are restarted or migrated, which may make
users feel that the performance of their VMs degraded out of nowhere.

Regards,
Fabricio

On 2026/10/21 15:40:08 Vladimir Petrov wrote:
 > Hi all,
 >
 > As per some requests, I'm waiting for 2 more items to be finished and
then I'll announce the 4.22.2 code freeze. Here they are
 >
 > StorPool import support (almost ready, waiting for smoke tests to
finish):
 > https://github.com/apache/cloudstack/pull/14389
 > importVM Linstor support backport PR:
 > https://github.com/apache/cloudstack/pull/14388
 >
 > I expect this to happen later this week or beginning of next.
 >
 > Best regards,
 > Vladimir
 > ________________________________
 > From: Vladimir Petrov <[email protected]>
 > Sent: 07 October 2026 15:43
 > To: [email protected] <[email protected]>;
[email protected] <[email protected]>
 > Subject: Re: 4.22.2 Release plan
 >
 > Hi all,
 >
 > There are still some pending PRs that should go into 4.22.2 release
so I'm extending the code freeze again. The new date is 21 October 2026,
with first release candidate (RC) cut on 28 October 2026. Please ping me
or Suresh (@vladimirpetrov or @sureshanaparti) on your Github PRs and
issues if you want them to be included in the 4.22.2 milestone.
 >
 > Best regards,
 > Vladimir
 >
[cid:YFukUIcZ0ewXosJTb9S1wemailbanner_png]<https://www.cloudstackcollab.org>
 > ________________________________
 > From: Vladimir Petrov <[email protected]>
 > Sent: 24 September 2026 10:21
 > To: [email protected] <[email protected]>;
[email protected] <[email protected]>
 > Subject: Re: 4.22.2 Release plan
 >
 > Hi all,
 >
 > We would like to update the timeline for the 4.22.2 release plan:
 >
 >
 > *
 > Features/Improvements/Bug-fix Code Freeze: 7 October 2026
 > *
 > First Release Candidate (RC) cut: 14 October 2026.
 >
 > Please ping me or Suresh (@vladimirpetrov or @sureshanaparti) on your
Github PRs and issues if you want them to be included in the 4.22.2
milestone.
 >
 > Best regards,
 > Vladimir
 >
 >
[cid:YFukUIcZ0ewXosJTb9S1wemailbanner_png]<https://www.cloudstackcollab.org>
 > ________________________________
 > From: Vladimir Petrov <[email protected]>
 > Sent: 06 August 2026 17:29
 > To: [email protected] <[email protected]>;
[email protected] <[email protected]>
 > Subject: 4.22.2 Release plan
 >
 > Hi all,
 >
 > As proposed on [1], I will serve as the RM for the 4.22.2 release and
Suresh Anaparti will act as the co-RM, assisting with triage, reviews,
testing, merge and release work.
 >
 > We would like to announce the plan for our next minor LTS release
4.22.2, here is the proposed timeline for the release:
 >
 > Features/Improvements/Bug-fix Code Freeze: 23 September 2026.
 > First Release Candidate (RC) cut: 30 September 2026.
 >
 > All the open issues and PRs targeted for this release are tracked in
the 4.22.2 release milestone [2] in Github.
 >
 > Please ping us (@vladimirpetrov or @sureshanaparti) on your Github
PRs and issues that are to be included in the 4.22.2 milestone.
 >
 > Please let us know if you have any questions.
 >
 > [1] https://lists.apache.org/thread/xo9881d73hx4tfrj12q7wqx0l4j86t94
 >
 > [2] https://github.com/apache/cloudstack/milestone/46
 >
 > Regards,
 > Vladimir Petrov
 > [cid:ercAJzpk2NFWeksRlJ0QShapeBlue_logo_sml_png]
 > Vladimir Petrov
 > Staff QA Engineer
 > s: +44 203 603 0540
 > e: [email protected] | w: www.shapeblue.com <http://www.shapeblue.com> | t: @shapeblue  > a: 3 London Bridge Street, 3rd floor, News Building, London, SE1 9SG, UK
 >
[cid:YFukUIcZ0ewXosJTb9S1wemailbanner_png]<https://www.cloudstackcollab.org>
 > ________________________________
 >
 > Find out more about ShapeBlue and our range of CloudStack related
services:
 > IaaS Cloud Design &
Build<http://shapeblue.com/iaas-cloud-design-and-build/> | CloudStack
Consulting<http://shapeblue.com/cloudstack-consultancy/> | CloudStack
Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
 > CloudStack Infrastructure
Support<http://shapeblue.com/cloudstack-infrastructure-support/> |
CloudStack Bootcamp Training
Courses<http://shapeblue.com/cloudstack-training/>
 >
 > Shape Blue Ltd is a company incorporated in England & Wales.
ShapeBlue is a registered trademark. This email and any attachments to
it may be confidential and are intended solely for the use of the
individual to whom it is addressed. Any views or opinions expressed are
solely those of the author and do not necessarily represent those of
Shape Blue Ltd or related companies. If you are not the intended
recipient of this email, you must neither take any action based upon its
contents, nor copy or show it to anyone. Please contact the sender if
you believe you have received this email in error.
 >
 >
 >

Reply via email to