Received-SPF: pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: policy releases
To:     Russell Coker <russell@coker.com.au>,
        selinux-refpolicy@vger.kernel.org
References: <2086377.kClcD5v8Ks@liv>
From:   Chris PeBenito <pebenito@ieee.org>
Message-ID: <53267840-d958-b573-f4f7-0bb5b96b8e9c@ieee.org>
Date:   Mon, 25 Jan 2021 09:57:27 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <2086377.kClcD5v8Ks@liv>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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