Code Freeze Exception Request: KEP-5598 Opportunistic Batching

23 views
Skip to first unread message

Roman Baron

unread,
Jul 21, 2026, 10:01:13 AM (11 days ago) Jul 21
to releas...@kubernetes.io, kubernetes-...@googlegroups.com, sig-sch...@kubernetes.io
Hello Release Team,

I'd like to request a 7 calendar day code freeze exception for the following enhancement.

Enhancement name: Opportunistic Batching (KEP-5598)
Enhancement status: Beta (v1.37)
SIG: SIG Scheduling
k/enhancements issue: kubernetes/enhancements#5598
PR #s: 

Additional time needed: 7 calendar days (due Wednesday, July 29 AoE)

Reason this enhancement is critical for this milestone:
This PR is the final implementation PR for the current Beta scope of the Opportunistic Batching enhancement targeted for v1.37. The preceding implementation PRs have already merged: 

This PR completes the remaining implementation work for the current Beta scope and resolves the associated tracking issue. Without it, the enhancement would not be fully implemented in v1.37.

Reason the extension is needed:
The implementation is complete and the PR is currently under active review by SIG Scheduling maintainers. Since some of the reviewers are on planned vacation during the code freeze period, I'm requesting 7 calendar days to allow sufficient time for the review process, address any feedback, and get the PR merged.

Risks from adding code late:
The scope of this PR is limited to completing the existing implementation. It builds on functionality that has already been reviewed and merged, and I expect any remaining changes to be driven primarily by review feedback.

Risks from cutting the enhancement:
If this PR does not make the v1.37 release, the current Beta implementation of Opportunistic Batching would remain incomplete and the remaining work would need to be carried over to a future release.

Thank you for your consideration,
Roman Baron

Dominik Marcinski

unread,
Jul 21, 2026, 10:45:53 AM (11 days ago) Jul 21
to Roman Baron, releas...@kubernetes.io, kubernetes-...@googlegroups.com, sig-sch...@kubernetes.io
+1

--
You received this message because you are subscribed to the Google Groups "sig-scheduling" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sig-schedulin...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-scheduling/DS0PR12MB8575EA5A4816FE37AD0D56F2B5C22%40DS0PR12MB8575.namprd12.prod.outlook.com.

Kensei Nakada

unread,
Jul 22, 2026, 6:41:35 PM (9 days ago) Jul 22
to Roman Baron, releas...@kubernetes.io, kubernetes-sig-release, sig-sch...@kubernetes.io
+1

2026年7月21日(火) 22:57 'Roman Baron' via sig-scheduling <sig-sch...@kubernetes.io>:

Dipesh Rawat

unread,
Jul 24, 2026, 10:56:57 AM (8 days ago) Jul 24
to kubernetes-sig-release
Hi all,

After reviewing the request and the discussion in the referenced Slack thread [0], the Release Team is APPROVING this exception request for a 5 calendar day extension rather than the originally requested 7 days.

Based on the 5 calendar day extension, the updated deadline for this KEP is: Monday, 27th July 2026 (Anywhere on Earth) / Tuesday, 28th July 2026, 12:00 UTC.

Please note that all remaining reviews and pending work needs to be completed within this extension. Otherwise, this will need to be deferred to a future release.

If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.

Thanks,
Dipesh Rawat
v1.37 Release Lead

[0]: https://kubernetes.slack.com/archives/C2C40FMNF/p1784738747684859

Reply all
Reply to author
Forward
0 new messages