Facts surface about Cupcake elements in a new T-Mobile G1 update

[inportb]

Keyword being: "Cupcake elements"

As you no doubt know, cupcake is the current development branch, not a product in and of itself. As portions of the development branch become stable, they are merged into the master branch and eventually pushed to our devices.

So no, we're not going to get this "cupcake update" in just one OTA, nor is it an update at all. We'll just see new features appearing in future updates. They would no longer be called "cupcake" when we receive the features because that's just a development codename.

[DesignDawg]

As you no doubt know, cupcake is the current development branch, not a product in and of itself. As portions of the development branch become stable, they are merged into the master branch and eventually pushed to our devices.

So no, we're not going to get this "cupcake update" in just one OTA, nor is it an update at all. We'll just see new features appearing in future updates. They would no longer be called "cupcake" when we receive the features because that's just a development codename.

Actually, Cupcake was merged with the master branch weeks ago. Just FYI.

[inportb]

I know. Not all of it, though. And by no means does merging to master mean instantaneous availability as an end-user patch.

[rynosaur]

Oh my, I just never get tired of this tomato/tomatoe argument about RC31 being elements thereof or the whole shootin' match deployment of the main development branch. This is how I'm spending precious moments of my life, participating in arguments over hypothetical minutiae

[inportb]

Ah, vocabulary does get you places, right? =D

Most of the people who're worried about cupcake had never experienced OSS development before, heh.

[rynosaur]

Ah, vocabulary does get you places, right? =D

Most of the people who're worried about cupcake had never experienced OSS development before, heh.

Yeah, I hear you. Add in the Tmo/HTC proprietary drivers and secret deployment schedules and you have a lot of wierd openness/closedness issues. It's like reporting on close-door hearings in Congress

And if vocabulary gets me anywhere, I'll send you a postcard when I get there.

[DesignDawg]

I know. Not all of it, though. And by no means does merging to master mean instantaneous availability as an end-user patch.

Nor did I say that it did mean that. But you said Cupcake is a development branch (which is only kida true now...), and that it would be merged to master in small pieces (which was not the case when it merged). Do you have a link that says "not all of it" was merged?

The fact that it is unfinished is well-documented. But that doesn't mean it's not merged.

From http://source.android.com/roadmap/cupcake

Update: cupcake has been merged into master.

[inportb]

Oh well... I'm not in that much of a hurry to get some cupcake. I'm not even sure how OTA works on WiFi, heh. The new features look nice, though.

If it does I'd hop on the vocabulary bandwagon too.

@DesignDawg:
They only tell us what would be merged to master, but not everything that's been going on with cupcake. To find that out we'd look at the source. I did not say that the code would be merged in small pieces, but we do know that opensource software is modular and tends to be developed in portions. For example, the target kernel must have been merged because all other development depends on it.

[rynosaur]

Oh well... I'm not in that much of a hurry to get some cupcake. I'm not even sure how OTA works on WiFi, heh. The new features look nice, though.

If it does I'd hop on the vocabulary bandwagon too.

Erm? Your possible snark does not compute.

For a real updayyt on what v1.5 firmware does and does not do as of this very moment: try Google. All your bases are belong to them.

[inportb]

Oh, right. I get data off WiFi and I'm pretty happy with the Android stack on the most part.