netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: iptables release plans
Date: Mon, 21 Mar 2011 19:48:54 +0100	[thread overview]
Message-ID: <4D879D96.2000904@trash.net> (raw)

About a potential iptables release for 2.6.38 - we don't have any
new features in the kernel that would require a new release.
However we've had a lot of other changes that would be good to
get out for wider testing.

Unfortunately due some confusion at the time of the last kernel
release, all patches for the upcoming feature in 2.6.39 have been
added to the master branch. I don't want to release extensions
for new kernel features while we're in the -rc phase since we
might still decide to change the userspace API.

So the options basically are:

- branch off the current HEAD, remove all new extension for upcoming
  features and release that branch

- skip the release for 2.6.38

Any opinions?

             reply	other threads:[~2011-03-21 18:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 18:48 Patrick McHardy [this message]
2011-03-21 19:48 ` iptables release plans Jan Engelhardt
2011-03-21 22:43   ` Patrick McHardy
2011-03-21 23:22     ` Jan Engelhardt
2011-03-21 21:09 ` Jozsef Kadlecsik
2011-03-21 22:44   ` Patrick McHardy

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=4D879D96.2000904@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.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 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).