The legend of Cupcake… how it go so ridiculously popular I am not sure. But the Android loving masses wanted a touchscreen keyboard and when the name “Cupcake” surfaced, people never took their eyes off it. They wanted it. They needed it. But now they are going to Homer Simpson it.
The next dev branch of Android is called Donut.
Right now, Donut is identical to Cupcake and will be developed over time, mostly by Google but they are accepting submissions/updates/features from developers. We learn this from a discussion on Google Groups from April 26th:
branches with codenames (i.e. cupcake, donut), as well as the master branch, are evolving, they’re not frozen like tags.
There are tags for android-1.0, android-sdk-1.5-pre and android-1.5, which aren’t evolving.
Donut is the codename for the project that immediately follows cupcake (you can figure out the ordering by realizing that the codenames are in alphabetical order).
At this point, indeed, the code in donut is identical to that in cupcake. The focus has been primarily on cupcake, and while donut is ready to receive changes it hasn’t had any yet.
See that note about “Alphabetical Order”? We thought it would be fun to predict the possible names of the development branches for E through Z. My list is below, feel free to make your own suggestions in the comments!
- Jelly (Unfortunately, Jell-O is a brand name)
- Noodle (Nerds would be hilarious)
- Orange (Oreo would be better!)
- Quince (White men can’t jump / Jeopardy!)
- RockyRoad (uhoh, bad foreshadowing!)
- Taffee (Twinkee!)
- UDC (upside-down-cake)
- Xmas Cookies?
- Zebra Cake
As you can see I stuck with the dessert-ish theme but I suppose you could go in a more general “food” direction or even take it elsewhere. The Android dev branch naming pattern is like that of hurricanes every year… and both are on a path to destroy anything that comes in its way!
As for actual “practical” knowledge, Jean-Baptiste Queru imparts that upon us yet again in another thread on Google Groups:
Here’s the current situation:
-in each “code” repository:
- release-1.0 is the branch for 1.0 as it was originally released. It should be considered read-only (i.e. we don’t normally accept submissions into it).
- cdma-import is the branch that was used by Teleca (a member of OHA) to work on CDMA support in Android. read-only.
- cupcake is the branch that follows the cupcake source tree that exists inside Google. it’s read-only.
- donut is the branch for the first named project after cupcake. It’s still in the process of being set up. At the moment it’s still identical to cupcake. We might accept limited contributions into it at some point in the future (as we transition away from the model that we used for cupcake).master is the branch for all projects after donut. We accept contributions into it.
- android-1.0 tags the original 1.0 code drop.
- android-sdk-1.5-pre tags the 1.5 preview SDK. It’s the open-source part of the exact source that was used to build the SDK, so it can be used e.g. to match stack traces
- android-1.5 tags the official 1.5 release of the Android Open-Source Project. It’s the one that should be used by people porting Android 1.5 to devices.
-within the “manifest” repository:
- there are the same branches as in the “code” repositories, which point to the matching branches in all the code repositories.
- there are branches for android-1.5 and android-sdk-1.5-pre, which point to the matching tags in all the code repositories (those have to be branches as an artifact of the way repo currently works).
- there are the same tags as in the “code” repositories.
So there you have it… a little more information on the Donut, the naming pattern, and some fun guesses at the future dev branches! The question is, if Google has an oversized statue of each dev branch made, will the Google Campus start to look pervertedly similar to Michael Jackson’s Neverland Ranch?
Eclair is ALREADY confirmed as the next release after Donut.
After that my guess is FRIED DOUGH :)
Google And Blog
After Eclair, My Guess is Fritter!
really its great to know whats next… but can I please have a bite of cupcake now… I have been a good boy
Eclair, Fudgecake, GooeyChocolatePudding, HoneyRoastParsnips, IceCream, Jelly, KinderSurprise, LactoseFreeMilkSubstituteShake, Meat, Nougat, OohLookSomeLovelyCakes, Plum, QuornCake, RareSteak, Sugar, TomatoJuice, UgliFruit, VeryNiceCake, WalnutAndDateCake, XRayOfACake, YummyCake, ZucchiniCake
Yeah no joke. Lets stick to baked goods.
after eclair then maybe fudge would be a good name
They’ve already deviated from “baked” goods as donuts are normally fried, not baked.
Pork bone and Puha
Fudge would be a hilarious codename.
Does anybody know what A and B were?
A and B were named after robots (you know, Android…). The only deviation was Petit-Four (known by US end users as the RC33), named so because it was supposed to be a small update.
any word on what we’re going to get in this “donut” ?!!
@Bad Johnie: I think their naming scheme isn’t so much baked goods, as is pastries in whole.
@Maj: They already said that, at the moment, Donut is exactly the same as cupcake, as far as code and features go. When cupcake is out to everyone, they are going to start brainstorming for new features, and if you’re a dev, they will be taking input from the community, and possibly even putting in user generated code and ideas. So what it seems like is; in the near future, (sooner than we thought) Android is going to be run like a Linux distro. Meaning what goes into the code and the updates come more from the ideas and mandates of the masses, not from watery tarts distributing swords… I mean the proprietary code banks of the Win/Mac coders and suits who think they have a good idea on what people want, when they have no honest to god clue.
As far as them keeping up with said scheme, it would be awesome, and google certainly has the corporate size and pull to not give in to anyone saying it is childish and unprofessional. But part of me thinks that once the next iteration of the Android oS comes out , we’ll lose the update naming scheme in favor of something else. Kind of like what Windows and Mac have been doing. Who knows, maybe they’ll call that one Cyborg, and it will have different main dishes for the updates; I.E. Brisket, Chowder, Deviled Ham, etc.
Eclair, Frap, Hummus
What they should call it is… “Were gonna take a long a** time putting this update together, delay it for months and then slowly roll it out”
Yea…. that sounds right to me =)
meat ball please !!
Ha, I like Petit Four, which is also a baked good/pastry. Literally it means small oven in French and refers to a type of cookie… suitable for a minor release, me thinks.
Yeah, I want to see Twinkie but I think it is copy-written…
When can I get my cupcake…. I’m fiening for some right now!!
hey jerks, layoff the MJ jokes assholes.
Eclair (is fixxed)
Flan (is fixxed)
I agree Eclair, Flan, then maybe, Wafers or Strudel
After F… which i can’t come up wiht a creative name, G has to be Gumdrop.
Well seeing as eclair has been out for a few months now, As you may already know Flan is next, followed by ginger bread, followed by honey… not sure what comes with the letter I but i know J will be jello, and thats all that is known as of now.
Michael Martin seems to have an inside track. Nine months later and it sure looks like the whole project is turning into lots of Fried Dough!
F is officially going to be Froyo, for frozen yogurt
well what about fritter?
With the release of Eclair, Android is preparing the way for a giant deception of their userbase. A large number of pretty useless applications come preinstalled on devices with already cramped memory space.
Useless applications like the “gallery” and “file manager” which only work between themselves, and betray the promise of Android to the developer base (of which I am one) to really make a difference and give the User base the optimal user experience.
Then there are the Facebook, DivX, JavaME Apps, Clock, Layar, YouTube, MySpace and Music Player which many people do not like or do not need, but you cannot de-install all this junk form your Android Phone.
With Android giving the wrong example, developers will choose or are forced to build monolithic applications; Users will have to install 3 or 4 applications that do basically the same but one will do a particular function just a little bit better.
Do not get me wrong here: I believe in the Android concept – that is why I became an Android developer, but these issues need to be addressed. I wonder if Google is actually aware that the Android team is making Android’s fight with the competition so much harder than needed.
pubblish dope wars for donut
its actually cupcake, donut, eclair, froyo (frozen yogurt), and then gingerbread.
I work at Mountain View. The upcoming releases that Google just announced on our intranet is:
Ice Cream Sandwich (it sandwiches Honeycomb and Gingerbread)
Key Lime Pie