netdev - [ANN] Winter break shutdown plan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date: Tue, 5 Dec 2023 10:10:02 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: netdev@...r.kernel.org, netdev-driver-reviewers@...r.kernel.org
Cc: Kalle Valo <kvalo@...nel.org>, Johannes Berg
 <johannes@...solutions.net>, fw@...len.de, pablo@...filter.org,
 torvalds@...ux-foundation.org, bpf@...r.kernel.org
Subject: [ANN] Winter break shutdown plan

Hi!

tl;dr net-next will be closed Dec 23rd - Jan 1st (incl.)

Last year the winter holidays fell right after the v6.3 merge window.
We used this as an opportunity to extend the net-next shutdown over
the winter and new year's celebrations. The concept of shutting down
-next development seems to have overwhelming support, the real question
is whether to shut down for one or two weeks, rather than whether to
shut down at all.

The timing of the merge window is not as lucky this time. We will have
to do a "mid-cycle shutdown". net-next will "close" for feature
development, refactoring, etc. Because some code will exist in net-next
only, however, net-next will remain open for fixes. A bit confusing, but
hopefully we all understand what a fix is ;) Maybe a better way 
to phrase the shutdown this time would be "fixes only" rather than
"net-next is closed".

Regarding timing - we did a small poll among developers and/or
attendees of the bi-weekly call and the conclusion seems to be
that we should shut down on Dec 23rd (Saturday) and reopen on Jan 2nd.
Two-week shutdown had some support but it's hard to know whether to
fit the extra week before Christmas or after New Year or to split it...

Depending on the urgency and volume of fixes we hope to also skip
the PR to Linus on Dec 28th.

Hopefully the merge window for v6.8 will open on Jan 7th or 14th,
giving us at least a week to settle any -next code which is ready
after the break.

As always during net-next closures RFC posting of net-next code are
not be discouraged.