The release schedule for a new Android OS to an OEM (i.e. non-Nexus phone) is usually, if we're lucky, a few months before the next OS is announced/released to AOSP. This makes us power users/geeks frustrated, but it's really how it's supposed to be. Google releases a new OS and the OEMs get to work porting, polishing, and adding/deleting. The carriers then get to testing, and we eventually get a new OS rollout. Since Google's already done the testing/polishing/etc. for their specific device (latest Nexus), they roll it out immediately.
There is nothing wrong with this. This is how a truly open OS works. If Motorola, Samsung, et al get the OS long before it's released, it's not fair to the rest of the players and the average Joe/Jane who simply wants to compile a custom Android version for themselves (or their products). This is what happened with Honeycomb: Motorola pushed Google to get a true tablet OS out the door so they could compete with Apple. It failed for Motorola, and it frustrated a lot of people because the OS was never released to AOSP (Google, from what I hear, didn't really want it released at all and ICS was supposed to be the next OS after Gingerbread).
All of which is to say: No. This is not because Jelly Bean is coming out. Ice Cream Sandwich is coming out now because it's ready now (from Moto and VZW). I'd expect to see Jelly Bean sometime late this or early next year, so enjoy your ICS. 2012 should be the year of ICS, with some devices getting an update as late as early 2013 (and some not at all). Welcome to an open source OS.
Still, I can do far more on GB than I can on iOS 5, so it's all relative. I don't care about upgrades; I care about functionality. You can get a new Kia every year and feel good about having a great upgrade cycle for your vehicles; I'll happily churn along in my 2005 WRX with incremental upgrades as I go along. Functionality is king, and 2.3 Android is still years ahead of most other OSes in this regard (WP7 and iOS, mainly).
