Subject: Mir 0.20 release content

From: Alan Griffiths <[email-masked]>
Date: Thu, 11 Feb 2016 16:54:20 +0000

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

---

From: Cemil Azizoglu <[email-masked]>
Date: Thu, 11 Feb 2016 14:50:36 -0600

FYI, here are the dates for OTA-10 :

String/Feature freeze 2/23/2016
Final freeze and regression test starts 3/4/2016
Release 3/16/2016

Thanks,
Cemil

Cemil Azizoglu
Mir Display Server - Team Lead
Canonical USA

On Thu, Feb 11, 2016 at 10:54 AM, Alan Griffiths <
[email-masked]> wrote:

> --
> Mir-devel mailing list
> [email-masked]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/mir-devel
>

---

From: Daniel van Vugt <[email-masked]>
Date: Fri, 12 Feb 2016 09:22:23 +0800

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...