SELinux-Refpolicy Archive on lore.kernel.org
 help / Atom feed
* new release?
@ 2019-01-01 23:27 Russell Coker
  2019-01-02 23:44 ` Chris PeBenito
  0 siblings, 1 reply; 3+ messages in thread
From: Russell Coker @ 2019-01-01 23:27 UTC (permalink / raw)
  To: selinux-refpolicy

It's been over 6 months since the last release, could we have another release 
soon?

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: new release?
  2019-01-01 23:27 new release? Russell Coker
@ 2019-01-02 23:44 ` Chris PeBenito
  2019-01-05  1:50   ` Russell Coker
  0 siblings, 1 reply; 3+ messages in thread
From: Chris PeBenito @ 2019-01-02 23:44 UTC (permalink / raw)
  To: Russell Coker, selinux-refpolicy

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.

-- 
Chris PeBenito

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: new release?
  2019-01-02 23:44 ` Chris PeBenito
@ 2019-01-05  1:50   ` Russell Coker
  0 siblings, 0 replies; 3+ messages in thread
From: Russell Coker @ 2019-01-05  1:50 UTC (permalink / raw)
  To: Chris PeBenito; +Cc: selinux-refpolicy

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/




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-01 23:27 new release? Russell Coker
2019-01-02 23:44 ` Chris PeBenito
2019-01-05  1:50   ` Russell Coker

SELinux-Refpolicy Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/selinux-refpolicy/0 selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ https://lore.kernel.org/selinux-refpolicy \
		selinux-refpolicy@vger.kernel.org selinux-refpolicy@archiver.kernel.org
	public-inbox-index selinux-refpolicy


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.selinux-refpolicy


AGPL code for this site: git clone https://public-inbox.org/ public-inbox