From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: Re: lets think about 3.3 - 3.3-rc1 release release notes draft
Date: Mon, 06 Sep 2021 20:39:53 +0200 [thread overview]
Message-ID: <87k0jta6py.fsf@redhat.com> (raw)
In-Reply-To: <87pmtpa2wt.fsf@redhat.com>
I tried to pick only important things as there's a lot of fixes related
to static analysis and compiler warnings.
Please take a look and if you miss something or want improve message
let me know.
My plan is to announce 3.3-rc1 on Wed morning (CEST)
RELEASE 3.3-rc1
======================
User-visible changes
--------------------
* When reading a binary policy by checkpolicy, do not automatically change the version
to the max policy version supported by libsepol or, if specified, the value given
using the "-c" flag.
* `fixfiles -C` doesn't exclude /dev and /run anymore
* CIL: Lists are allowed in constraint expressions
* CIL: Improved situation with duplicate macro and block declarations
* Added the new `secilc2tree` program to write out CIL AST.
* Improved documentation
* A lot of Static code analyse issues and compiler warnings fixed
* Bug fixes
Development-relevant changes
----------------------------
* CIFuzz is turned on in CI
https://google.github.io/oss-fuzz/getting-started/continuous-integration/
* Fedora 34 image is used in CI
Issues fixed
------------
* https://github.com/SELinuxProject/selinux/issues/293
prev parent reply other threads:[~2021-09-06 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 13:18 lets think about 3.3 release Petr Lautrbach
2021-08-09 14:01 ` James Carter
2021-08-09 14:43 ` Dominick Grift
2021-08-15 20:21 ` Nicolas Iooss
2021-08-17 18:44 ` Petr Lautrbach
2021-09-03 8:05 ` Petr Lautrbach
2021-09-03 8:37 ` Dominick Grift
2021-09-03 12:45 ` James Carter
2021-09-03 14:12 ` Petr Lautrbach
2021-09-03 19:13 ` Petr Lautrbach
2021-09-06 18:39 ` Petr Lautrbach [this message]
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=87k0jta6py.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox