From: Petr Lautrbach <plautrba@redhat.com>
To: SElinux list <selinux@vger.kernel.org>
Subject: ANN: SELinux userspace 3.3-rc3 release candidate
Date: Wed, 06 Oct 2021 14:08:32 +0200 [thread overview]
Message-ID: <87k0iqz77j.fsf@redhat.com> (raw)
Hello,
A 3.3-rc3 release candidate for the SELinux userspace is now
available at:
https://github.com/SELinuxProject/selinux/wiki/Releases
Please give it a test and let us know if there are any issues.
If there are specific changes that you think should be called out
in release notes for packagers and users in the final release
announcement, let us know.
Thanks to all the contributors to this release candidate!
If there's no big change, I'd like to announce 3.3 release next
Wednesday.
Changes since 3.3-rc2
----------------------------------
* Updated checkpolicy documentation
* checkpolicy prints the reason why opening a source policy file failed
* Bug fixes
Shortlog of changes since the 3.3-rc1 release
-----------------------------------------------
Christian Göttsche (10):
Correct some typos
libsepol: ebitmap: mark nodes of const ebitmaps const
libsepol: use correct cast
libsepol: resolve GCC warning about null-dereference
libsepol/cil: silence clang void-pointer-to-enum-cast warning
checkpolicy: policy_define: cleanup declarations
checkpolicy: print reason of fopen failure
checkpolicy: update documentation
checkpolicy: drop incorrect cast
checkpolicy: delay down-cast to avoid align warning
James Carter (2):
libsepol/cil: Limit the amount of reporting for bounds failures
libsepol/cil: Do not skip macros when resolving until later passes
Nicolas Iooss (2):
README: update continuous integration badges
GitHub Actions: do not use macOS latest runner for now
Petr Lautrbach (2):
libselinux/semodule: Improve extracting message
Update VERSIONs to 3.3-rc3 for release.
reply other threads:[~2021-10-06 12:08 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=87k0iqz77j.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=selinux@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 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.