From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: Intent to release 3.1-rc1
Date: Tue, 5 May 2020 15:57:27 +0200 [thread overview]
Message-ID: <20200505135727.GD7308@workstation> (raw)
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
Hello,
I'd like to release 3.1-rc1 until end of this week.
Looking at https://patchwork.kernel.org/project/selinux/list/ I see:
- 3 acked patches which are ready to be merged (and I'll merge
them tomorrow if there's no other comment):
https://patchwork.kernel.org/patch/11525435/ libselinux: Add missing errno setup
https://patchwork.kernel.org/patch/11527311/ tree-wide: introduce PYTHON_SETUP_ARGS to customize setup.py calls on Debian
https://patchwork.kernel.org/patch/11527463/ Travis-CI: upgrade to Ubuntu 18.04 and latest releases of Python and Ruby
- 1 patchset which should be postpone for the next release as it breaks setools
https://lore.kernel.org/selinux/20200502190828.3555858-1-omosnace@redhat.com/T/#t
- 1 patch without response:
https://patchwork.kernel.org/patch/11392367/ libselinux/getconlist: add verbose switch to print more information
- 1 RFC related to other kernel RFC
https://patchwork.kernel.org/patch/11436953/ [RFC] selinux: add unprivileged sandboxing capability
https://patchwork.kernel.org/patch/11436955/ [RFC] libsepol,secilc,policycoreutils: add unprivileged sandboxing capability
There are 2 opened github PRs without Signed-of: and matching patch on the
mailing list:
https://github.com/SELinuxProject/selinux/pull/174 Use quote include for files located in the local directory
https://github.com/SELinuxProject/selinux/pull/135 More robust ausearch time input
Have I missed something? Do you have any comments, objections to release?
Petr
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-05-05 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:57 Petr Lautrbach [this message]
2020-05-05 14:21 ` Intent to release 3.1-rc1 Christian Göttsche
2020-05-05 14:28 ` Petr Lautrbach
2020-05-05 14:22 ` Stephen Smalley
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=20200505135727.GD7308@workstation \
--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.