- cross-posted to:
- android
- cross-posted to:
- android
The new dessert codename reflects the change in Android’s build process that made Google start the lettering over again.
You must log in or register to comment.
🥷 Android Balaclava
So the went Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, Ice Cream Sandwich , Jellybean, KitKat, Lollipop, Marshmallow, Nougat, Oreo, Pie, and then 10 (Quince Tart), 11 (Red Velvet Cake), 12 (Snowcone), 13 (Tiramisu), 14 (Upsidedown Cake), 15 (Vanilla Ice cream), and then they started over at B for Baklava? Weird.
I mean… This post literally includes the excerpt from the article about why. It’s literally the only thing in the OP other than the link itself.
Yeah, but even understanding that, it’s still weird to start over at B.
Yeah, at least W should have been easy enough. I can understand dodging X, Y and Z. But then why start at B?
Save you a click:
However, if you’ve been following Android platform development news lately, you may have heard of something called the trunk stable project. Without getting too technical, the way that Google develops Android has significantly changed. The first Android version to be released as part of the trunk stable project was Android 14 QPR2 back in March, which is why that release used a very different build ID naming scheme. Instead of having build IDs that started with the letter “U” for Upside Down Cake, Android 14 QPR2 had build IDs that started with the letter “A.”
That makes no sense. Wouldn’t that make Android 15 B and 16 C?
¯_(ツ)_/¯
Didn’t they stop doing the dessert names a few versions ago? Android Pie I think?
The internal code names are still desserts. Public release names are just numbered.
Would have been funny if they used a different type of fruit, like fruit/veg
Android 17, 🍆
Android 18 🍑
Android 19 💩
It’s always been desserts or sweets
Yeah, but since it flipped back to A
