From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Etienne Champetier <champetier.etienne@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: iptables 1.8.5 ETA ?
Date: Wed, 6 May 2020 14:09:09 +0200 [thread overview]
Message-ID: <20200506120909.GA10344@orbyte.nwl.cc> (raw)
In-Reply-To: <20200506120012.GA21153@salvia>
Hi,
On Wed, May 06, 2020 at 02:00:12PM +0200, Pablo Neira Ayuso wrote:
> On Wed, May 06, 2020 at 07:44:12AM -0400, Etienne Champetier wrote:
> > Hi All,
> >
> > Pablo told me 3 weeks ago that "It might take a few weeks to make the
> > new release."
> > (https://bugzilla.netfilter.org/show_bug.cgi?id=1422#c13)
> >
> > I'm sure it'll be release when it's ready :) but do you see an
> > iptables release happening this month ? (to know if I should just wait
> > or go ask maintainers for backports)
Luckily, the month has just begun. ;)
> Cc'ing Phil. He's got some pending work to push it out.
Seriously, I wanted to push it already but then discovered some leaks
here and there. To improve coverage, I implemented a valgrind mode into
shell testsuite. This helps identify old and new issues, I'm trying to
fix them all at once. Will fold into the cache rework series what's
introduced by that and keep the rest separate.
Expect a series showcasing the additional changes and new commits today
or tomorrow. If there are no complaints, I'll push everything out until
the end of this week.
If above goes well, maybe release next week to leave at least a small
margin for any fallout to show up?
Cheers, Phil
next prev parent reply other threads:[~2020-05-06 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 11:44 iptables 1.8.5 ETA ? Etienne Champetier
2020-05-06 12:00 ` Pablo Neira Ayuso
2020-05-06 12:09 ` Phil Sutter [this message]
2020-05-06 12:34 ` Pablo Neira Ayuso
2020-05-06 12:40 ` Etienne Champetier
2020-05-26 13:36 ` Etienne Champetier
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=20200506120909.GA10344@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=champetier.etienne@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).