Mir 0.20 release content

[Daniel van Vugt]

I've been thinking we should probably address this before the next release:
https://bugs.launchpad.net/mir/+bug/1536662

And while Brandon has a fix prepared for USC to stop it happening at 
login, it can still happen elsewhere:
https://bugs.launchpad.net/mir/+bug/1541188

So although what I'm about to propose is technically less secure (not 
sure if it's less secure anywhere that matters though), it would give us 
a reliable system at least: Fall back to /dev/urandom if /dev/random is 
blocking and not sufficiently ready. Anything is better than crashing as 
we are now...


On 12/02/16 00:54, Alan Griffiths wrote:
> Hi,
>
> I'll be starting the 0.20 release process tomorrow AM with the aim to
> hit OTA10.
>
> I'm not aware of any MPs still in flight that are required for this
> release, if you know of any please speak up.
>
> Regards,
> Alan
>