From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Cc: Kalle Valo <kvalo@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
fw@strlen.de, pablo@netfilter.org, torvalds@linux-foundation.org,
bpf@vger.kernel.org
Subject: [ANN] Winter break shutdown plan
Date: Tue, 5 Dec 2023 10:10:02 -0800 [thread overview]
Message-ID: <20231205101002.1c09e027@kernel.org> (raw)
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.
next reply other threads:[~2023-12-05 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 18:10 Jakub Kicinski [this message]
2023-12-06 2:01 ` [ANN] Winter break shutdown plan Alexei Starovoitov
2023-12-21 15:00 ` Paolo Abeni
2023-12-21 18:09 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231205101002.1c09e027@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=fw@strlen.de \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.