netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Kalle Valo <kvalo@kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	Matthieu Baerts <matttbe@kernel.org>
Subject: [ANN] net-next shutdown plans around LPC
Date: Tue, 20 Aug 2024 11:30:34 -0700	[thread overview]
Message-ID: <20240820113034.73448a88@kernel.org> (raw)

Hi!

LPC 2024 will begin less than a month from now, on Sept 18th.

The conference will take place very close to the merge window 
(either during the first week of the merge window, or the week
before it). Since a lot of the maintainers and reviewers will 
be attending LPC, netconf, maintainer summit etc. - we plan 
to shut down net-next on Sept 13th (end of the week before LPC).

If Linus cuts final 6.11 on the 15th - this will be a non-event.
If he doesn't - we will operate for a week with 2 trees in 
"fixes only mode", with net-next only accepting fixes for
code already in it (and net operating as usual).

For sub-trees which feed net-next, we would appreciate if
the PRs were posted by Sept 12th. We may still pull extra
stuff the week of LPC if merge window doesn't open, but
would prefer not to :)

 - netdev maintainers

                 reply	other threads:[~2024-08-20 18:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240820113034.73448a88@kernel.org \
    --to=kuba@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=daniel@iogearbox.net \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=matttbe@kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev-driver-reviewers@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=steffen.klassert@secunet.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).