SELinux Security Module development
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: Re: lets think about 3.3 release
Date: Fri, 03 Sep 2021 21:13:06 +0200	[thread overview]
Message-ID: <87pmtpa2wt.fsf@redhat.com> (raw)
In-Reply-To: <87zgsu9j9c.fsf@redhat.com>

Petr Lautrbach <plautrba@redhat.com> writes:

> Petr Lautrbach <plautrba@redhat.com> writes:
>
>> 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.
>
>
> Currently patchwork contains just these patches which should be relevant
> to 3.3:
>
> https://patchwork.kernel.org/patch/12435365/ New [1/2] libsepol/cil: Improve in-statement to allow use after inheritance
> https://patchwork.kernel.org/patch/12435363/ New [2/2] libsepol/secilc/docs: Update the CIL documentation
>
> These are probably superseeded already, but I'm not sure. Please take a look.
>
>
> https://patchwork.kernel.org/patch/12470297/ New [1/3,v2] libsepol/cil: Remove redundant syntax checking
> https://patchwork.kernel.org/patch/12470301/ New [2/3,v2] libsepol/cil: Use size_t for len in __cil_verify_syntax()
> https://patchwork.kernel.org/patch/12470299/ New [3/3,v2] libsepol/cil: Fix syntax checking in __cil_verify_syntax()
>
> Wait for review.
>
> So I think selinux-3.3-rc1 can be released on next Wednesday 2021-09-08
>
> If you have any concerns, comments or suggestion, let us know.
>
> Also I really don't understand all the changes in libsepol so please help me
> to collect release notes information for it. I'll post a release notes
> draft with other components later today.
>

I'm sorry but I won't make it today. I have to leave it on Monday
morning.


Petr


  parent reply	other threads:[~2021-09-03 19:13 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 [this message]
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=87pmtpa2wt.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