Now that the Galaxy Nexus will be officially updated to Android 4.1 Jelly Bean next week (partly to bypass an injunction blocking their sale in the U.S.), many of you are no doubt wondering when your favorite ROMs will be updated to Google's latest and greatest. So far, AOKP, BAMF, and CyanogenMod have announced their plans for bringing you your custom Jelly Bean fix. CyanogenMod's Jelly Bean ROM will go by the name CyanogenMod 10, or CM10, while AOKP will be called... wait for it... AOKP. BAMF plans to continue calling its Galaxy Nexus ROM Paradigm following the update to Jelly Bean, though it might see a version number bump to 2.0 for its first JB iteration.

CM10: The Legacy Continues
In CyanogenMod's Google+ post, the team (as spoken for by Steve Kondik) explains why the next generation of CyanogenMod will not be called CM9.1 due to Android only getting a .1 added to its version number - basically, for every alphabetical version of Android going forward, there will be a corresponding 1.0 increment added to CyanogenMod's version number. Just as Android 2.2 Froyo was CM6, Gingerbread was CM7, CM skipped a version number for Honeycomb, and Ice Cream Sandwich is CM9, Android 4.1 Jelly Bean will be CM10 (and, following the pattern, Key Lime Pie, whether it ends up as Android 4.2 or Android 5.0, will be CM11). Consequently, CM's version number will always correspond to the position of the first letter of Android's latest iteration in the alphabet ("I" for "Ice Cream Sandwich" is the 9th letter of the alphabet, "J" for "Jelly Bean" is the 10th, and so on).

Will your phone get CM10? Well, if it meets CM's requirements for CM9 (such as a minimum 512MB of RAM), then yes, it will. CyanogenMod will not maintain separate device trees for CM9 and CM10, which means that the first official stable version of CM9 will also be the last. From that point on, CyanogenMod will be providing updates only to CM7 and CM10. CyanogenMod's Google+ post states that CM10 will not have to be rewritten from the gound up, as CM9 did going from CM7 (as any informed Android user can attest to, Ice Cream Sandwich was a quantum leap from Gingerbread, so CM's enhancements had to take that same leap). For this reason, it should not take nearly as long for CM10 to get up and running after Jelly Bean source drops. As is the rule for CyanogenMod, though, the ETA for CM10 will be "when it's ready.

AOKP: A "Milestone" followed by a milestone
In AOKP's case, ICS will see one more "stable" release in Milestone 6, which Team Kang hopes to have ready sometime this weekend. Unlike CyanogenMod, AOKP is making its first leap to a new version of Android, and Team Kang will be rewriting its enhancements from the ground up for Jelly Bean. You can expect the code overhaul to be far more significant than simply going from, say, Build 39 to Build 40, and even more significant than going from Milestone 5 to Milestone 6. Consequently, the first official Jelly Bean version of AOKP will NOT be coming immediately after source drops (even CyanogenMod isn't just going to spit out a new Jelly Bean build right after source is released). It will take time for Team Kang to rewrite its code from the ground up, but your patience will be rewarded.

BAMF: A New Paradigm
According to my discussion with Erishasnobattery, Team BAMF, unlike AOKP, does not plan to rewrite its enhancements from the ground up for Jelly Bean, and expects a relatively seamless transition from ICS to Jelly Bean. It should be noted that, since BAMF Paradigm only runs on the three Galaxy Nexus variants, it does not rely on the CM codebase and its device/vendor trees, so it may be out of the gate with Jelly Bean more quickly. Other than some layouts and visual tweaks to match Jelly Bean's new style, the transition for BAMF should be pretty straightforward.

Invitation to all ROM developers
Please feel free to contact me with your Jelly Bean plans via PM here on Rootzwiki if you want me to incoporate them into this article. I intend for it to be a live roadmap of everyone's Jelly Bean update plans. While you're at it, you could send me a file of your ROM's logo if you want me to incorporate it into the article graphic.

Imagine the Possibilities
Just thinking about all the amazing things that CyanogenMod and Team Kang will no doubt be doing with new Jelly Bean features such as the new notification feature and Google Now is exciting. What can you envision? A pink unicorn background for Google Now? Setting options for which "cards" you want to see in ROM Control? CyanogenMod's Cid mascot giving you your weather forecast? The possibilities are endless, but don't let that stop you from expressing your ideas in the comments below!

ROM Roadmap Updates
iceandfire from Team Horizon: XenonHD will be reworked from the ground up for Jelly Bean for stability and code merge issues.