All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Jason Zaman <jason@perfinion.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: ANN: SELinux userspace 2.8-rc3 release candidate
Date: Wed, 23 May 2018 13:16:18 -0400	[thread overview]
Message-ID: <ab37bde9-1900-1900-e62f-2a83109d9108@tycho.nsa.gov> (raw)
In-Reply-To: <20180516173138.GA12679@baraddur.perfinion.com>

On 05/16/2018 01:31 PM, Jason Zaman wrote:
> Just a quick note in case the release is soon.
> I have a couple patches to make everything work on
> Musl libc that im gonna clean them up and post in the morning.

Given that these have been merged and I've seen no other activity, I assume we can make a final 2.8 release anytime.
If anyone objects, speak up now.

> 
> On Thu, May 10, 2018 at 11:20:01AM -0400, Stephen Smalley wrote:
>> A 2.8-rc3 release candidate for the SELinux userspace is now available at:
>> https://github.com/SELinuxProject/selinux/wiki/Releases
>>
>> Please give it a test and let us know if there are any issues.
>>
>> A draft of the release notes is available from the Releases page, as
>> is the full git log output and git shortlog output since the 2.7
>> release.  If there are further items we should mention or if something
>> should be amended in the release notes, let us know.
>>  
>> Thanks to all the contributors to this release candidate!
>>  
>> A shortlog of changes since the 2.8-rc2 release candidate is below.
>>
>> Stephen Smalley (7):
>>       libsepol: remove unused function and type
>>       libselinux: fix build warning in save_booleans()
>>       libselinux: avcstat: fix build warning
>>       libselinux: audit2why: fix build warnings
>>       libsemanage: prevent string overflow on final paths
>>       libsepol: cil: prevent stack buffer overflow in cil_expr_to_string
>>       Update VERSION files to 2.8-rc3
>>
>> Vit Mojzis (1):
>>       python/semanage/seobject.py: Fix undefined store check
> 
> 

  reply	other threads:[~2018-05-23 17:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 15:07 ANN: SELinux userspace 2.8-rc1 release candidate Stephen Smalley
2018-04-20 12:31 ` Petr Lautrbach
2018-04-20 12:49   ` Stephen Smalley
2018-04-20 13:31     ` Petr Lautrbach
2018-04-20 14:09       ` Stephen Smalley
2018-04-25 14:11         ` Yuli Khodorkovskiy
2018-04-25 14:32           ` Stephen Smalley
2018-04-23 20:00 ` Nicolas Iooss
2018-04-26 17:35 ` ANN: SELinux userspace 2.8-rc2 " Stephen Smalley
2018-05-03 14:52   ` Last call for selinux userspace 2.8 release Stephen Smalley
2018-05-04  7:55     ` Jason Zaman
2018-05-04 13:08       ` Stephen Smalley
2018-05-04 13:26         ` Dominick Grift
2018-05-04 13:36           ` Stephen Smalley
2018-05-04 14:26             ` Jason Zaman
2018-05-04 14:43             ` Dominick Grift
2018-05-04 12:19     ` Dominick Grift
2018-05-04 13:09       ` Stephen Smalley
2018-05-04 13:16         ` Dominick Grift
2018-05-04 14:30           ` Petr Lautrbach
2018-05-10 15:20   ` ANN: SELinux userspace 2.8-rc3 release candidate Stephen Smalley
2018-05-16 17:31     ` Jason Zaman
2018-05-23 17:16       ` Stephen Smalley [this message]
2018-05-23 17:45         ` Jason Zaman
2018-05-24 19:21     ` ANN: SELinux userspace release 20180524 / 2.8 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=ab37bde9-1900-1900-e62f-2a83109d9108@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=jason@perfinion.com \
    --cc=selinux@tycho.nsa.gov \
    /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.