Trying to understand
In this release you removed the lulzactive governor control module(one of my favorite parts by the way, it worked really well) and upgraded the kernel. You also widgified the torch and added power button functionality for the camera, battery status tweaks and several other enhancements.
In past updates there were some with many more additions that only increased your versioning by trailing decimal, and others that only receive a patch level...
I really want to understand why you chose to version this release at 3.0 instead of something like 2.1 and am hoping maybe you can shed some light on good rules of thumb to follow for maintaining ROM updates. If I can ever resolve VM heaping issues in Eclipse on this crappy old PC of mine I may actually turn out my own ROM, but to do so and maintain it I would want to know that I am not going to waste my time because of the time it takes my single core 3.1 GHz Intel processor to compile all the source, not to mention the eclipse tweaks I have to perform frequently to avoid the VM heaping issues.
Any help you can provide will be greatly appreciated.
By the way, because I absolutely love the combination of CM9 2.0 with Black Infinitum Theme, I will not be upgrading again until next AOSP release or CM9 implements its own theming finally. More control over how my software looks and Icon packs... That leads me to an entirely new thought and question, has anyone ever attempted to make an app that attempts to decompile apk, modify xml and recompile apk on the fly to have granular control over the SystemUI?
All that to say this, Thanks again to all the effort in bringing us Cyanogen.