[10:51] <alan_g> greyback: I was wondering about doing another miral release. Do you think we're ready? If so, should it be a pure bugfix cherry-pick (0.2.1) or what we have on trunk (0.3.0 with the new ABIs)?
[10:53] <greyback> alan_g: there are a couple of ABI breaking changes qtmir needs, I think trunk is more suitable
[10:53] <alan_g> greyback: ABI isn't *breaking*!!! Just additions.
[10:54] <greyback> err, yes, ABI changes, sorry bad phrasing
[10:54] <alan_g> ;)
[10:55]  * alan_g is a bit over-sensitive as not breaking ABI was (and is) the original point of miral
[10:56] <alan_g> greyback: any thoughts on the active reviews?
[10:57] <greyback> alan_g: not yet, on my list for after lunch
[10:58] <alan_g> np. will leave them for you
[15:11] <greyback> alan_g: can you do a quick sanity check for me. In the mir client api, is there an api to modify an existing MirSurfaceSpec to adjust the surface position (aka edit rect the surface should attach to)
[15:12] <greyback> instead the only way I see to do that is to create a new spec with mir_connection_create_spec_for_{menu,tip}
[15:12] <alan_g> 0.25
[15:12] <greyback> bah
[15:12] <greyback> release it already! :)
[15:12] <alan_g> But creating a new spec works
[15:13] <alan_g> that's what anpok did in gtk-mir
[15:13] <greyback> it does, it's just a bit more work (have to remember parent & pixelformat)
[15:14] <greyback> I mir_surface_spec_set_placement has appeared
[15:14]  * alan_g doesn't like how long it takes to release mir functionality
[15:42] <alan_g> greyback: would you cast a proofreading eye over this? https://code.launchpad.net/~alan-griffiths/miral/changelog-0.3.0/+merge/308245
[15:42] <greyback> ok
[15:45] <greyback> alan_g: looks fine
[15:45] <alan_g> thanks
[15:50] <greyback> alan_g: quickie I missed: https://code.launchpad.net/~gerboland/miral/fix-miral-qt-ftbfs/+merge/308273
[15:51] <alan_g> greyback: Approved
[15:51] <greyback> thanks