From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: Re: Intent to release 3.2-rc1
Date: Mon, 18 Jan 2021 15:59:39 +0100 [thread overview]
Message-ID: <874kjeffz8.fsf@redhat.com> (raw)
In-Reply-To: <87h7nka15c.fsf@redhat.com>
Petr Lautrbach <plautrba@redhat.com> writes:
> Petr Lautrbach <plautrba@redhat.com> writes:
>
>> Hello,
>>
>> It's more than half a year since 3.1-rc1 and more than a year since
>> 3.0-rc1 so I'd like to start with 3.2 release process. If there's no
>> objection and no unexpected issues I'd announce 3.2-rc1 release on the
>> next Wednesday, January 13.
>>
>> According to patchwork there are several patches not accepted:
>>
>> https://patchwork.kernel.org/patch/11436955/ New [RFC] libsepol,secilc,policycoreutils: add unprivileged sandboxing capability
>>
>> without any reaction for a long time
>>
>>
>> https://patchwork.kernel.org/patch/11668455/ New selinux: make use of variables when defining libdir and includedir
>>
>> Nicolas raised some concerns and asked for a reproducer, without any
>> other response.
>>
>>
>> https://patchwork.kernel.org/patch/11993081/ New [1/6] libsepol: do not decode out-of-bound rolebounds
>> https://patchwork.kernel.org/patch/11993085/ New [2/6] libsepol: ensure that hashtab_search is not called with a NULL key
>>
>> I read it as there are some changes requested and therefore need to be updated.
>>
>>
>> https://patchwork.kernel.org/patch/11993087/ New [3/6] libsepol/cil: constify some strings
>> https://patchwork.kernel.org/patch/11993089/ New [4/6] libsepol/cil: fix NULL pointer dereference when parsing an improper integer
>> https://patchwork.kernel.org/patch/11993083/ New [5/6] libsepol/cil: fix out-of-bound read in cil_print_recursive_blockinherit
>> https://patchwork.kernel.org/patch/11993091/ New [6/6] libsepol/cil: destroy perm_datums when __cil_resolve_perms fails
>>
>> Ack-ed, probably could be merged.
>>
>>
>> https://patchwork.kernel.org/patch/11940309
>> https://github.com/SELinuxProject/selinux/pull/273
>>
>> The patch on the mailing list is not up to date with the PR and needs to
>> be resent.
>>
>>
>
> The current situation:
>
> https://patchwork.kernel.org/patch/11993081/ New [1/6] libsepol: do not decode out-of-bound rolebounds
> https://patchwork.kernel.org/patch/12001639/ New newrole: preserve environment variable XDG_RUNTIME_DIR
> https://patchwork.kernel.org/patch/12002081/ New [1/2] libsepol/cil: Update symtab nprim field when adding or removing datums
> https://patchwork.kernel.org/patch/12002083/ New [2/2] libsepol/cil: Fix heap-use-after-free in __class_reset_perm_values()
> https://patchwork.kernel.org/patch/12006921/ New [1/2] libselinux: accept const fromcon in get_context API
> https://patchwork.kernel.org/patch/12006923/ New [2/2] libselinux: update getseuser
> https://patchwork.kernel.org/patch/12011663/ New python/sepolgen: allow any policy statement in ifndef
> https://patchwork.kernel.org/patch/12017871/ New [v2,1/2] setfiles: Do not abort on labeling error
>
> I'd like to defer rc1 for few days due to the lack of time and number
> of unmerged patches.
>
> Sorry for the inconveniences.
Lets do -rc1 on this wednesday and in case not all open changes are
reviewed merge them to 3.2-rc2
Release notes draft is available at
https://plautrba.fedorapeople.org/selinux/20210118/RELEASE-3.2-rc1.txt
Please review and tell me whether you're missing something.
Petr
prev parent reply other threads:[~2021-01-18 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:40 Intent to release 3.2-rc1 Petr Lautrbach
2021-01-13 23:05 ` Petr Lautrbach
2021-01-18 14:59 ` 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=874kjeffz8.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