From: Russell Coker <russell@coker.com.au>
To: Chris PeBenito <pebenito@ieee.org>
Cc: "selinux-refpolicy@vger.kernel.org" <selinux-refpolicy@vger.kernel.org>
Subject: Re: new release?
Date: Sat, 05 Jan 2019 12:50:38 +1100 [thread overview]
Message-ID: <4273847.YW0sMm4lCG@liv> (raw)
In-Reply-To: <c9e21feb-f51f-14f0-f197-b51ef6f72b52@ieee.org>
On Thursday, 3 January 2019 10:44:19 AM AEDT Chris PeBenito wrote:
> On 1/1/19 6:27 PM, Russell Coker wrote:
> > It's been over 6 months since the last release, could we have another
> > release soon?
>
> I suppose so. There haven't been many changes lately, so a release
> hasn't seemed pressing.
https://lists.debian.org/debian-devel-announce/2018/04/msg00006.html
Above is the summary of the Debian/Buster freeze schedule. After the 12th of
Feb new source packages will not be accepted. I'd like to have a policy
source package newer than July 2018 in Buster so a new upstream release later
this month would work well. I don't expect you to go out of your way for my
convenience, but I think you would probably prefer that distributions not have
too old releases of policy to reduce the weird support questions. So any time
a distribution that supports SE Linux is about to have a freeze and there
hasn't been a refpolicy release for a while is probably a good time for it.
As for not many changes, there are ~1500 lines of patches in git since the
2.20180701. I've just submitted about 1000 lines of patches and can easily
submit another 500 lines or so before the end of the month. I think we can
double or triple the patch size against the last release over the course of
the next few weeks. Increased patch size isn't the aim of course, but it will
hopefully correlate to the amount of fixes for problems that affect users.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2019-01-05 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 23:27 new release? Russell Coker
2019-01-02 23:44 ` Chris PeBenito
2019-01-05 1:50 ` Russell Coker [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=4273847.YW0sMm4lCG@liv \
--to=russell@coker.com.au \
--cc=pebenito@ieee.org \
--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).