All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: SElinux list <selinux@vger.kernel.org>
Cc: James Carter <jwcart2@gmail.com>,
	Dominick Grift <dominick.grift@defensec.nl>
Subject: Re: lets think about 3.3 release
Date: Fri, 03 Sep 2021 16:12:54 +0200	[thread overview]
Message-ID: <87v93hagt5.fsf@redhat.com> (raw)
In-Reply-To: <CAP+JOzSmoDp_9XhoXXghu9HL=H3iXPFWAVkN_AnDxbhdDRRF2g@mail.gmail.com>

James Carter <jwcart2@gmail.com> writes:

> On Fri, Sep 3, 2021 at 4:38 AM Dominick Grift
> <dominick.grift@defensec.nl> wrote:
>>
>> 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
>>
>> Strictly speaking these can probably wait until after 3.3 although it would
>> be nice to get this in.
>>
>> Maybe eventually some day in the distant future we can re-consider
>> disallowing duplicate macro and block declarations in favor of this functionality.
>>
>> >
>> > These are probably superseeded already, but I'm not sure. Please take a look.
>> >
>
> They are waiting for the three patches below, so they can all be
> merged together.
>
>> >
>> > 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.
>> >
>
> The only changes are what Nicolas suggested when he reviewed them, so
> I don't think it will be too long before these will be merged. I don't
> have anything else other than these.
>

Great, thanks!

Petr



>
>
>
>> > 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.
>> >
>> >
>> > Thanks,
>> >
>> > Petr
>> >
>> >
>>
>> --
>> gpg --locate-keys dominick.grift@defensec.nl
>> Key fingerprint = FCD2 3660 5D6B 9D27 7FC6  E0FF DA7E 521F 10F6 4098
>> https://sks-keyservers.net/pks/lookup?op=get&search=0xDA7E521F10F64098
>> Dominick Grift


  reply	other threads:[~2021-09-03 14: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 [this message]
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=87v93hagt5.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --cc=dominick.grift@defensec.nl \
    --cc=jwcart2@gmail.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.