From: Russell Coker <russell@coker.com.au>
To: selinux-refpolicy@vger.kernel.org
Subject: policy releases
Date: Wed, 20 Jan 2021 23:07:23 +1100 [thread overview]
Message-ID: <2086377.kClcD5v8Ks@liv> (raw)
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?
As an aside I've got just over 7000 lines of patches against the current Git
refpolicy. I'm aiming to get that below 3500 lines before the release.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2021-01-20 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 12:07 Russell Coker [this message]
2021-01-25 14:57 ` policy releases Chris PeBenito
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=2086377.kClcD5v8Ks@liv \
--to=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 NNTP newsgroup(s).