Linux 7.4 merge window opens with 6,753 changesets — and could stretch to three weeks
The merge window for Linux 7.4 is open, and the pace of incoming work is already substantial: 6,753 non-merge changesets have been pulled into the mainline repository so far, according to LWN.net, which published the first instalment of its merge-window coverage in "The first part of the 7.4 merge window." Many more are expected before the window closes — particularly because, as LWN notes, there is a possibility that this merge window will be extended to three weeks rather than the usual two.
That three-week extension remains a possibility only; no confirmed schedule has been announced. The changeset figure of 6,753 should likewise be read as a snapshot at the time of LWN's report rather than a final tally for the cycle — the count will keep climbing for as long as the window stays open, and readers can audit it directly against the mainline git shortlog.
What a merge window actually is
For readers less immersed in kernel process: the merge window is the roughly two-week period after each release during which subsystem maintainers send their pull requests to Linus Torvalds for the next version. Only after the window closes does the two-week regression-fixing stabilisation period begin, leading to the final release. Everything merged during the window is therefore subject to change — bugs found during stabilisation can still be fixed or reverted before 7.4 ships.
Even this initial batch, LWN reports, brought in a number of new features alongside the continued general cleanups and security fixes that the kernel has seen in recent cycles. LWN's full subsystem-by-subsystem breakdown sits behind its paywall; the underlying pull requests and Torvalds's merge announcement remain publicly readable on LKML, and the public git shortlog offers a complete record of the incoming work for anyone who wants to audit it directly.
Why a three-week window matters
An extended merge window would be more than a scheduling curiosity. It would push back the start of stabilisation, and with it the release date of 7.4, which in turn ripples into the planning horizons of distribution vendors, cloud providers and hardware enablement teams that track upstream milestones. Teams that budget a fixed interval between kernel releases — for qualification cycles, backport schedules or hardware bring-up — may need to absorb an extra week of slippage if the extension happens.
For enterprise and ARM/server infrastructure operators in particular, the practical takeaway from a still-open window is restraint: the feature set is not final, the changeset count is provisional, and any verdict on what 7.4 does or does not deliver should wait until the window closes and the merge-window reports have run their full course.
LWN.net's coverage of the 7.4 merge window continues as more subsystem pull requests land. The authoritative record remains Torvalds's LKML announcements and the mainline git shortlog.
Source: LWN.net, "[$] The first part of the 7.4 merge window", https://lwn.net/Articles/1101211/
Linux 7.4 merge window 開啟，已收錄 6,753 個 changeset —— 且可能延長至三週
Linux 7.4 的 merge window 已正式開啟，而 incoming 工作的步伐已相當可觀：根據 LWN.net 報導，至今已有 6,753 個非 merge 的 changeset 被 pull 進 mainline repository。LWN 已發表其 merge window 系列報導的首篇〈The first part of the 7.4 merge window〉。在 window 結束前，預料還會有更多 changeset 加入 —— 尤其因為 LWN 指出，這次 merge window 有可能由慣常的兩週延長至三週。
不過，三週延長目前只是可能性之一，官方尚未公布確認時間表。同樣地，6,753 個 changeset 這個數字應理解為 LWN 報道時的快照，而非整個周期的最終統計 —— 只要 window 仍然開放，數字便會持續上升，讀者亦可直接對照 mainline git shortlog 進行審核。
merge window 究竟是什麼
對於不太熟悉 kernel 流程的讀者：merge window 是每個 release 之後約為期兩週的時段，各 subsystem maintainer 會在此期間向 Linus Torvalds 發出下一版本的 pull request。要待 window 結束後，為期兩週、用於修復 regression 的 stabilisation 階段才會展開，最終 release 亦由此產生。因此，在 window 期間 merge 的一切內容仍可能變動 —— 在 stabilisation 期間發現的 bug，仍可在 7.4 正式推出前修正或 revert。
LWN 報道指出，即使只是這初步一批，除了近期各周期一直進行的一般性清理及安全性修復外，亦引入了不少新功能。LWN 按 subsystem 逐一列出的詳細分析設於其付費牆之內；相關的 pull requests 及 Torvalds 的 merge 公告則仍然可在 LKML 公開閱讀，而公開的 git shortlog 亦為任何希望直接審核的人士提供完整的 incoming 工作記錄。
為何三週 window 值得關注
延長的 merge window 不單是排程上的趣聞。它會推遲 stabilisation 的開始時間，從而推遲 7.4 的 release 日期，並進一步影響發行版本商、雲端服務供應商及硬件 enablement 團隊的規劃時間表 —— 該等團隊均會追蹤 upstream 里程碑。對於在 kernel release 之間預留固定間隔以安排認證周期（qualification cycle）、backport 排程或硬件 bring-up 的團隊而言，若延長成真，他們可能需要承受多一週的延誤。
對企業及 ARM／伺服器基建維護人員尤其而言，window 仍未關閉所帶來的實際啟示是克制：feature set 尚未最終確定，changeset 數目只是臨時數字，任何關於 7.4 提供或不提供什麼的結論，都應等到 window 結束、merge window 報導全部出齊後才作定論。
隨着更多 subsystem pull request 陸續到來，LWN.net 對 7.4 merge window 的報導將持續更新。最具權威性的記錄，仍然是 Torvalds 在 LKML 的公告及 mainline git shortlog。
來源：LWN.net，〈[$] The first part of the 7.4 merge window〉，https://lwn.net/Articles/1101211/