CyanogenMOD Team Drops a Status Update on CM10 and all of the Jelly Bean Happenings
Yesterday was a huge day in the Android community. As I’m sure you know by now, the Jelly Bean source code was officially released, which means nothing but full steam ahead for developers looking to work on Android 4.1.
As I’m sure you are all anxious to learn about the progress of CM10, I figured I’d drop you a quick post to bring you up to speed on what’s going on behind the scenes at the CyanogenMOD camp. A few hours ago, the team took to Google+ to let the world know that they are already hard at work on the latest incarnation of the most popular custom ROM series on the planet. Here’s what they had to say:
Jelly Bean Status Update
Repositories for all AOSP projects have been created on our github to alleviate any potential mismatches (branch is ‘jellybean’).
While Jelly Bean won’t require a major rewrite of all the CM features, the source has been re-arranged and re-factored enough that a simple merge isn’t possible. So we will proceed with manual merging (this was to be expected really).
The plan of attack will be to cherry-pick everything from CM9 and fix the merge conflicts and relocations. It’s tedious but the only way. Ideally the original patch authors will forward-port their changes, so if you are out there and want to help out, join us in #cyanogenmod -dev.
+ Trebuchet might be messy to rebase onto JB.
+ Theme Engine will be messy.
+ SystemUI stuff will need to be restyled.
+ Lockscreen stuff will need to be restyled.
+ The current UX of Settings is good, no reason to change anything there.
A manifest (Cyanogenmod/android.git) will be going up later this afternoon, so the masses will be able to sync directly from our source at that point as well.
This will be it on the updates (so we can focus on actually working). Next post referencing JB should be when the merge/cherry-pick process is complete.
This is awesome news, as it won’t take nearly as long to get CM10 up and running as it did for CM9, even though it won’t go as quickly as we’d all wished for. We’ve also heard that all CM9 devices should receive CM10 support, so that should be a reason to breathe easier for a whole bunch of us, myself included.
We’ll be sure to keep you in the loop as more info rolls out. Stay tuned!