All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: lets think about 3.3 release
Date: Fri, 06 Aug 2021 15:18:41 +0200	[thread overview]
Message-ID: <87fsvmu2xa.fsf@redhat.com> (raw)

Hello,

I's about 184 commits and 5 months since the last release so I think
it's time to slowly stop the development and start with 3.3 release
candidates.

According to patchwork, there are few patches in queue which need to be
reviewed, or which were reviewed and some change for requested:

* https://patchwork.kernel.org/patch/11436955/ New [RFC] libsepol,secilc,policycoreutils: add unprivileged sandboxing capability
* https://patchwork.kernel.org/patch/11668455/ New selinux: make use of variables when defining libdir and includedir

old, without any activity for a long time

* https://patchwork.kernel.org/patch/12291637/ New [v2] checkpolicy: fix the leak memory when uses xperms

changes requested

* https://patchwork.kernel.org/patch/12372487/ New [v2] libselinux: add lock callbacks
* https://patchwork.kernel.org/patch/12377593/ New libselinux/utils: drop requirement to combine compiling and linking

no response yet

* https://patchwork.kernel.org/patch/12420657/ New [userspace]  libsepol/cil: remove obsolete comment

acked, ready to be merged

* https://patchwork.kernel.org/patch/12422971/ New mcstrans: Improve mlstrans-test output

no response yet


if I missed something please tell me.


There's one issue opened on the mailing list

https://lore.kernel.org/selinux/874kc57220.fsf@defensec.nl/T/#t -
libsepol regressions

If you agree and there's no obejction I can start with preparation and
plan to release 3.3-rc1 on Wed Aug 18 2021


Petr


             reply	other threads:[~2021-08-06 13:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 13:18 Petr Lautrbach [this message]
2021-08-09 14:01 ` lets think about 3.3 release 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     ` lets think about 3.3 - 3.3-rc1 release release notes draft Petr Lautrbach

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=87fsvmu2xa.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.