From: Chris PeBenito <pebenito@ieee.org>
To: Russell Coker <russell@coker.com.au>, selinux-refpolicy@vger.kernel.org
Subject: Re: policy releases
Date: Mon, 25 Jan 2021 09:57:27 -0500 [thread overview]
Message-ID: <53267840-d958-b573-f4f7-0bb5b96b8e9c@ieee.org> (raw)
In-Reply-To: <2086377.kClcD5v8Ks@liv>
On 1/20/21 7:07 AM, Russell Coker wrote:
> Refpolicy releases tend to be between 4 and 8 months apart. The last release
> was 5 months ago. So by past standards a new one could be any time soon.
>
> https://release.debian.org/bullseye/freeze_policy.html
>
> The Debian release schedule has a freeze on new source packages on 2021-02-12.
> To get from Unstable to Testing takes 5 days so new sources have to be
> uploaded on the 6th of Feb at the latest to get in. Would it be possible to
> have a new refpolicy release some time before the 5th of Feb so the next
> release of Debian can be as close as possible to upstream?
Yes. I was waiting on the dead module removals, but now that is complete, we
can move forward with a release. Merge window for this release will close at
noon on Feb 2 (UTC-4) for release on Feb 3.
--
Chris PeBenito
prev parent reply other threads:[~2021-01-25 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 12:07 policy releases Russell Coker
2021-01-25 14:57 ` Chris PeBenito [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=53267840-d958-b573-f4f7-0bb5b96b8e9c@ieee.org \
--to=pebenito@ieee.org \
--cc=russell@coker.com.au \
--cc=selinux-refpolicy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).