Verizon Galaxy Nexus loses Google support?

Did the Galaxy Nexus get caught in the middle of a lovers' quarrel between Google and Verizon today?
That's the way it appeared at first with the news that Google had dumped the CDMA version of Android's flagship phone. A reader first tipped off Droid Life that the CDMA/LTE version of the phone (read: Verizon) had been removed from Google's developer site, the Android Open Source Project, and replaced with a note reading, "No CDMA devices are supported."
The Ice Cream Sandwich-flavored handset had appeared on the site as recently as last week, but on the Google Code site, the factory image for the Verizon Galaxy Nexus--code-named Toro--now appears under "archived, for reference only."
It's sad for such a nice device to be kicked to the curb so harshly, but it doesn't appear to be the only device to get the boot. The CDMA Motorola Xoom and Sprint Nexus S 4G have also been removed.
Android Open Source & Compatibility Tech Lead Dan Morrill posted an explanation of sorts over in the Android Contributors Google Group. Here's the meat of his somewhat technical explanation:

Did the Galaxy Nexus get caught in the middle of a lovers' quarrel between Google and Verizon today?
That's the way it appeared at first with the news that Google had dumped the CDMA version of Android's flagship phone. A reader first tipped off Droid Life that the CDMA/LTE version of the phone (read: Verizon) had been removed from Google's developer site, the Android Open Source Project, and replaced with a note reading, "No CDMA devices are supported."
The Ice Cream Sandwich-flavored handset had appeared on the site as recently as last week, but on the Google Code site, the factory image for the Verizon Galaxy Nexus--code-named Toro--now appears under "archived, for reference only."
It's sad for such a nice device to be kicked to the curb so harshly, but it doesn't appear to be the only device to get the boot. The CDMA Motorola Xoom and Sprint Nexus S 4G have also been removed.
Android Open Source & Compatibility Tech Lead Dan Morrill posted an explanation of sorts over in the Android Contributors Google Group. Here's the meat of his somewhat technical explanation:




