Comment 182 for bug 862430

>>177-181

This is the dark side of the LTS coin. The plan is to continue security updates and minor bug fixes so long as nothing requires redesign, causes bugs, or adds new features until the next LTS; unfortunately, that includes the DE. I haven't looked through all of the code, but it seems this fix is part of a major change in compiz's rendering method, and even results in other bugs.

I think the real problems are compiz's (missing) roadmap and scattered community.

Take a look at the bzr where "Compiz has 210 active branches owned by 24 people and 10 teams. There were 311 commits by 11 people in the last month." It's good to see activity, but it's beyond me how this gets organized into a stable release whenever it does--particularly because there's no published discussion of the various tests being done or options being explored. If you want the latest news you'll have to get on IRC.

There are no blueprints for compiz. The last blueprint for compiz-core called for splitting it into 0.9.7.x (precise) and 0.9.8.x (oneric and beyond), which was done. The only published information about where compiz is going can be found in the targets for the next milestone (0.9.7.12 for precise), where this bug has been pushed up once again.

Last I checked, only Dainel and Sam work on compiz full-time, so handling all the bugs on a reasonable schedule is more than somewhat challenging. Still, I think the project would benefit from a revival of the compiz web as I pointed out in bug 880649. If we can bring back the forum, update the wiki, and get more volunteers interested in contributing to compiz then we can probably get better releases on a better schedule.