From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: New release?
Date: Mon, 30 Nov 2020 23:30:35 -0500 [thread overview]
Message-ID: <5562559.MhkbZ0Pkbq@x2> (raw)
In-Reply-To: <10188dab-63c3-4bc3-e950-37a9b3d7ac73@debian.org>
Hello,
On Sunday, November 29, 2020 6:37:36 PM EST Laurent Bigonville wrote:
> The freeze of the new debian release is approaching (early next year)
> and I'm looking a bit for guidance about what do with the audit package.
>
> Should I start cherry-picking patches, wait for a new (pre-)release?
> Keep the good 2.8?
The good 2.8 is rotten. It has not been patched for a very long time. Fedora
and RHEL are running off of github snapshots. I usually do a prerelease
tarball for everyone else to follow along with so that we can all stay in
sync. Hopefully, you have been using those.
The pre-release is perfectly good releases. I have been holding off on
calling it 3.0 because the major feature was container support. This has been
perpetually almost done for the last 5 years. I apologize for holding the
release up for something that is always out of reach, yet almost done.
I have one open question on:
https://github.com/linux-audit/audit-userspace/pull/134
and I think that might wrap things up for 3.0. We cannot wait for the
container work. It seems like the patch above is missing the use of a
AUDIT_FEATURE_BITMAP_ extension and then we are good to go.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-12-01 4:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 23:37 New release? Laurent Bigonville
2020-12-01 4:30 ` Steve Grubb [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-01 23:27 new release? Russell Coker
2019-01-02 23:44 ` Chris PeBenito
2019-01-05 1:50 ` Russell Coker
[not found] <Pine.LNX.4.64.0606052002530.5498@g5.osdl.org>
2006-06-06 6:02 ` New release? Junio C Hamano
2006-06-06 8:30 ` Johannes Schindelin
2006-06-06 10:27 ` Junio C Hamano
2006-06-06 12:42 ` Johannes Schindelin
2006-06-06 15:20 ` Junio C Hamano
2006-06-06 16:08 ` Jon Loeliger
2006-06-06 17:15 ` Junio C Hamano
2006-06-06 17:58 ` Jon Loeliger
2006-06-06 16:19 ` Pavel Roskin
2006-06-06 16:46 ` Nick Hengeveld
2006-06-06 18:38 ` Pavel Roskin
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=5562559.MhkbZ0Pkbq@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.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 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.