The fix for this bug in compiz being released with milestone 0.9.8.0 is good news, although it's not obvious how this will resolve the issue for users of 12.04.
* Will compiz milestone 0.9.8.0 be released with ubuntu milestone ubuntu-12.04.2?
* Will compiz milestone 0.9.8.0 be pushed to precise-updates, precise-proposed or precise-backports before the release of ubuntu-12.04.2?
* This bug is affects compiz-wall-plugin and compiz-plugins-main which both have fixes commited, does the fix for this issue require patches to all 3 packages?
* When the fixes are released for compiz-wall-plugin and compiz-plugins-main, will they be pushed to precise-proposed or precise-backports before the release of ubuntu-12.04.2?
It seems to me that the developers of these packages are coordinating to release fixes to their packages for the next SRU, 12.04.2; however, prior to the release of 12.04.1 it seems that the developers where coordinating to release the fixes for 12.04.1.
I can't speak for the 100 other people affected by this bug but following the release of 12.04.1, I would appreciate an update on how these fixes are being released, and when we can expect this issue to be resolved for users of 12.04.
The fix for this bug in compiz being released with milestone 0.9.8.0 is good news, although it's not obvious how this will resolve the issue for users of 12.04.
* Will compiz milestone 0.9.8.0 be released with ubuntu milestone ubuntu-12.04.2?
* Will compiz milestone 0.9.8.0 be pushed to precise-updates, precise-proposed or precise-backports before the release of ubuntu-12.04.2?
* This bug is affects compiz-wall-plugin and compiz-plugins-main which both have fixes commited, does the fix for this issue require patches to all 3 packages?
* When the fixes are released for compiz-wall-plugin and compiz- plugins- main, will they be pushed to precise-proposed or precise-backports before the release of ubuntu-12.04.2?
It seems to me that the developers of these packages are coordinating to release fixes to their packages for the next SRU, 12.04.2; however, prior to the release of 12.04.1 it seems that the developers where coordinating to release the fixes for 12.04.1.
I can't speak for the 100 other people affected by this bug but following the release of 12.04.1, I would appreciate an update on how these fixes are being released, and when we can expect this issue to be resolved for users of 12.04.