Release extravaganza: CM 11.0 and 12.0 Final

AKA “The Phantom Release”

As we look forward to Android M’s release later this year and continue work to integrate the latest from Android 5.1.1_r5 (released yesterday), we are finalizing the branches of CM11.0 and CM12.0. They have seen improved stability and security fixes over the past few months, but little in the way of further development as the focus shifted to CM12.1.



Tonight, the final snapshot releases of both 11.0 and 12.0 are going live – available in sequence as they are built out by our Jenkins instance.

Why another CM11 build? Rather surprisingly, many users have been slow to upgrade to L – whether due to the lack of a snapshot release or adverse reaction to the Material design, we don’t know. The meager stats that we have show that there is a rather large contingency of users who are sticking to CM11 as their release channel of choice, so we felt compelled to give a release showcasing all the work that went into that branch to make it ship ready.

There shouldn’t be any ‘gotchas’ with regards to flashing these builds for CM11 or CM12 users (minus the obligatory warning to make sure your gapps and etc match the Android version you are using). Upgrades should go through without issues, though many 11.0 users updating to 12.0 are advised to update their recoveries as well to ensure that SELinux support doesn’t give you a headache.

12.1 nightly users should not be compelled to downgrade to these releases.

Nightlies and weeklies for 11 and 12.0 branches will be slowly phased out, most likely shut off come M’s entry to nightlies. CM12.1 nightlies will continue as we prepare a release build for 5.1.1 as well (no ETA, sorry).

As always, bug reports can be submitted via our JIRA instance – though in all honesty CM11 issues are unlikely to see massive work, unless they prove to be ultra critical. CM12.0 bugs are fair game, as the code base between 12.0 and 12.1 are similar enough, and the bug likely impacts both branches if present.

Happy Flashing,

The CyanogenMod Team

No comments:

Post a Comment