After 3 rounds of release candidates, and squashing a few more bugs in the stabilization branch of CyanogenMod 7, the newest stable iteration of the Gingerbread-based CM7 is now being released. The team would like to thank everyone who submitted and followed up on bugs during the RC phase and helped us all get a better 7.2 out there, we couldn’t have done it without all of you, and we’re happy to say most of the devices slated for RC1 ended up getting a stable release today.
As mentioned in the RC1 post, “7.2 adds a couple of backported features and fixes from Android 4 (ICS), over 20 new devices when compared to 7.1, and even some new features to boot (be sure to check out the new predictive contact search in the phone dialer!). We’ve also fixed some bugs along the way. Some of them device-specific, others that affected everybody, and one in particular that’s been plaguing Android for a long time: the mysteriously vanishing SD-card ringtones are no more! You can check the full list of noteworthy changes at the CHANGELOG“.
7.2 also marks the end of the Gingerbread story for some hardware; as phones and tablets “graduate” to an ICS-based CM9 stable release, they will have their CM7 development frozen. That will very soon include the Nexus S devices, and probably a handful of others; for these devices, 7.2.0 will be the last Gingerbread release we do.
It is not, however, the end of the line for CM7. As mentioned before, development for CM7 will continue, even if at a slower pace, for devices that need it. We believe that a device in which IceCream Sandwich degrades functionality shouldn’t get CM9 at all, and since not all hardware is (for various reasons) capable of supporting ICS, there is no set date (nor tentative, nor a plan) to terminate work on CyanogenMod 7.x. We’ll be accepting the contribution of a few new devices very soon, and after a few weekly builds those will probably end up getting their very own 7.2.0 release. We’ll keep reviewing and accepting new device submissions to that version, if they happen. And we’ll keep supporting these devices for as long as we can (or until they can get CM9, whichever comes first )
And for last… We acknowledge that some minor/non-critical/unsolvable-at-the-moment issues reported to us were left unresolved; and that some more light (or even serious) problems may have slipped through the RC test stage and be unknown to us; so, as usual, we encourage you to submit any issues you find with these builds through our bug tracker.