Subject: [ANNOUNCE] Mir 0.1.9

From: Kevin Gunn <[email-masked]>
Date: Wed, 30 Apr 2014 08:17:51 -0500

Hi all,
As some may have been following, we've taken a step to introduce
non-blocking swapbuffers which was a result of investigation around a
particular toolkit behavior as well as a lengthy discussion with a variety
of industry partners. The test feedback was very good with some minor
regressions. So, I've tagged v0.1.9 on our development-branch:

https://launchpad.net/mir/utopic/0.1.9

We are in the midst of validating this to promote this to archive and into
the Touch image, hopefully today. Also, this will be the first release into
Utopic.

br,kg

---

From: Daniel van Vugt <[email-masked]>
Date: Thu, 01 May 2014 09:37:04 +0800

If you're using a touch device with 60Hz display, the glitches you 
notice in 0.1.9 should be minimal. But if you're one of the rare people 
with a refresh rate significantly different to 60Hz, then it might be a 
better idea to stick with 0.1.8. Read on in:
https://bugs.launchpad.net/mir/+bug/1308843

But all will be fixed in 0.2.0.

On 30/04/14 21:17, Kevin Gunn wrote:
> particular toolkit behavior as well as a lengthy discussion with a
> variety of industry partners. The test feedback was very good with some
> minor regressions. So, I've tagged v0.1.9 on our development-branch:
>
> We are in the midst of validating this to promote this to archive and
> into the Touch image, hopefully today. Also, this will be the first
> release into Utopic.
>
> br,kg
>
>
>

---

From: Daniel van Vugt <[email-masked]>
Date: Thu, 01 May 2014 14:03:26 +0800

Mir 0.1.9 has now hit utopic:
https://launchpad.net/ubuntu/+source/mir

Although the landing process must have changed because the 0.1.9 
packages were released without anything landing in lp:mir yet(!?).

---

From: Michał Sawicz <[email-masked]>
Date: Thu, 01 May 2014 09:08:36 +0200

> packages were released without anything landing in lp:mir yet(!?).

Kicked the merge & clean job and everything's in trunks now.

-- 
Michał (Saviq) Sawicz <[email-masked]>
Canonical Services Ltd.

---

From: Kevin Gunn <[email-masked]>
Date: Thu, 1 May 2014 08:49:37 -0500

> > packages were released without anything landing in lp:mir yet(!?).
Yes - the current "ci-train process" actually uploads binaries built from
that process so there is a window of time which trunk is "behind" archive.

br,kg

---

From: Daniel van Vugt <[email-masked]>
Date: Fri, 02 May 2014 09:20:31 +0800

No problem. Next time we should be sure the proposal is top-approved 
first. It wasn't top approved in this case so there was a real risk that 
people like me could make further changes without knowing those changes 
were too late to reach archive.

On 01/05/14 21:49, Kevin Gunn wrote:
> <[email-masked] <mailto:[email-masked]>> wrote:
>
> Yes - the current "ci-train process" actually uploads binaries built
> from that process so there is a window of time which trunk is "behind"
> archive.
>
> br,kg
>

---

From: Michał Sawicz <[email-masked]>
Date: Fri, 02 May 2014 08:46:15 +0200

> were too late to reach archive.

FYI, it's actually safe in the sense that those changes would just not
get into trunk. What gets pushed is a snapshot of trunk + branches being
merged at the time of source package preparation.

---

From: Daniel van Vugt <[email-masked]>
Date: Fri, 02 May 2014 14:52:41 +0800

Sure, not disastrous. Just that fixes documented (in the proposal) as 
being fixed in "0.1.9" may not actually have made it into the package. 
So inaccurate. It's nice to have accurate info about where things are 
fixed :)

---

From: Michał Sawicz <[email-masked]>
Date: Fri, 02 May 2014 08:58:09 +0200

> So inaccurate. It's nice to have accurate info about where things are

Of course, if there were things to still be fixed with a proposal, it
would be too late anyway indeed - unless you were in time to pull the
package back from proposed.

Don't get me wrong, not disagreeing here, just making sure we know
what's happening.