> The master branch is definitely not a release. It's the mainline, the
> trunk, the unstable. As such, almost by definition, it has issues
> (and, in this case, very major issues).

> At this point, nobody on the Android team has any visibility over its
> exact state beyond what can be seen in a few minutes (media is busted,
> orientation doesn't switch properly, several apps crash at launch, the
> runtime crashes frequently...).

> Cupcake is probably a lot more stable, though even in that case we
> have little visibility over the exact state of the open-source tree.

> JBQ

> On Tue, Mar 24, 2009 at 1:57 AM, Rajesh S <rajeshs...@gmail.com> wrote:

> > Thanks JBQ & Scott, am trying it out but what could be expected 'not
> > to work' on this branch? Would like to see if the expected to work
> > components are fine enough.

> > And could you give a rough idea of the differences between this branch
> > and a typical release. There are some apparent ones. Some aren't. Like
> > somebody had a good point about not so smooth scrolling on this
> > branch. Anyway it would be very useful to see even the obvious list of
> > differences from somebody in the Android team.

> > Thanks,
> > Rajesh.S

> > On Mar 24, 1:37 am, Jean-Baptiste Queru <j...@android.com> wrote:
> >> [still bcc android-platform, android-framework, android-porting]

> >> We're now one step closer. Change 9356 was submitted, so that the
> >> source tree "as is" can be compiled.

> >> You still need to set BUILD_WITHOUT_PV=true.

> >> JBQ

> >> On Sat, Mar 21, 2009 at 10:35 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> > [still bcc android-platform, android-framework, android-porting]

> >> > Latest status:

> >> > -we're back to one patch: 9356.

> >> > -build with "BUILD_WITHOUT_PV=true make"

> >> > -quickly tested both on emulator and dream, and seems to work well
> >> > enough to not have the phone app crash in a loop.

> >> > -I expect to submit 9356 on Monday morning PDT.

> >> > JBQ

> >> > On Sat, Mar 21, 2009 at 11:50 AM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> >> I've been working on a "better" batch of patches (now it feels more
> >> >> like open-heart surgery with a meat cleaver):

> >> >> -no need to delete the opencore directory or to remove it from the manifest.

> >> >> -you need to repo download changes 9355, 9356 and 9357. No need to
> >> >> take 9300. I know it's 3 changes instead of 1, because I had to touch
> >> >> a few more parts of the system, but those are much cleaner.

> >> >> -only tested on the emulator, so those might very well cause
> >> >> regressions on dream.

> >> >> JBQ

> >> >> On Thu, Mar 19, 2009 at 1:07 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> >>> I've put together a hack that allows the system to compile and start
> >> >>> all the way to the home app. I worked with the delicateness of
> >> >>> open-heart surgery performed with a chainsaw.

> >> >>> Steps:

> >> >>> -remove the opencore files ( rm -rf external/opencore
> >> >>> .repo/projects/external/opencore.git ). Remove opencore from your
> >> >>> .repo/manifest.xml if you intend to repo sync the entire world but
> >> >>> don't want to have to remove opencore every single time.

> >> >>> -patch in change 9300 ( repo download platform/frameworks/base 9300/1 )

> >> >>> -most probably do a clean build ( rm -rf out/ ; make )

> >> >>> I've "tested" on a device/release/generic/userdebug build. On my
> >> >>> machine, it compiles, launches. The media process dies (which probably
> >> >>> means that downloads are busted too), as well as the music player. The
> >> >>> browser starts and can access the network.

> >> >>> JBQ

> >> >>> On Wed, Mar 18, 2009 at 7:57 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> >>>> I've submitted the merge (106 projects!), and I believe that the tree
> >> >>>> is in the state that it should be.

> >> >>>> Caveats:

> >> >>>> -THE BUILD IS BROKEN. You've been warned. There's been some drift
> >> >>>> around OpenCORE (probably situations where new code was written in
> >> >>>>cupcakethat uses OpenCORE 1, or where APIs were removed incupcake
> >> >>>> that OpenCORE 2 relies on).

> >> >>>> The proper command to try to merge the OpenCORE code should be "git
> >> >>>> merge remotes/korg/cupcake" (I'm typing from memory).

> >> >>>> -I'm not 100% sure that the server contains exactly what it should.
> >> >>>> I've had a filesystem failure right as I was trying to verify it, and
> >> >>>> I'm not gonna be able to verify until at least sometime tomorrow.

> >> >>>> JBQ

> >> >>>> On Wed, Mar 18, 2009 at 12:43 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> >>>>> I expect to start submitting the changes in about an hour, i.e.
> >> >>>>> between 1:30pm and 2pm PDT.

> >> >>>>> Starting right now, you may want to avoid initiating a new repo sync,
> >> >>>>> unless you're OK ending up with a tree that might not even compile.

> >> >>>>> JBQ

> >> >>>>> On Tue, Mar 17, 2009 at 6:35 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> >> >>>>>> [bcc android-platform, android-framework, android-porting]

> >> >>>>>> I'm working on merging the latestcupcakecode drop into master. The
> >> >>>>>> task is quite hairy, so the following two guidelines probably apply:

> >> >>>>>> -please don't submit anything in gerrit, as you'll just get in my way.
> >> >>>>>> -now is a good time to repo sync master, as I'm going to have to
> >> >>>>>> submit the result of the merge in a state where it doesn't build, and
> >> >>>>>> I have no idea how long it'll take to get it to build again after
> >> >>>>>> that.

> >> >>>>>> Thanks,
> >> >>>>>> JBQ

> >> >>>>>> --
> >> >>>>>> Jean-Baptiste M. "JBQ" Queru
> >> >>>>>> Android Engineer, Google.

> >> >>>>>> Questions sent directly to me that have no reason for being private
> >> >>>>>> will likely get ignored or forwarded to a public forum with no further
> >> >>>>>> warning.

> >> >>>>> --
> >> >>>>> Jean-Baptiste M. "JBQ" Queru
> >> >>>>> Android Engineer, Google.

> >> >>>>> Questions sent directly to me that have no reason for being private
> >> >>>>> will likely get ignored or forwarded to a public forum with no further
> >> >>>>> warning.

> >> >>>> --
> >> >>>> Jean-Baptiste M. "JBQ" Queru
> >> >>>> Android Engineer, Google.

> >> >>>> Questions sent directly to me that have no reason for being private
> >> >>>> will likely get ignored or forwarded to a public forum with no further
> >> >>>> warning.

> >> >>> --
> >> >>> Jean-Baptiste M. "JBQ" Queru
> >> >>> Android Engineer, Google.

> >> >>> Questions sent directly to me that have no reason for being private
> >> >>> will likely get ignored or forwarded to a public forum with no further
> >> >>> warning.

> >> >> --
> >> >> Jean-Baptiste M. "JBQ" Queru
> >> >> Android Engineer, Google.

> >> >> Questions sent directly to me that have no reason for being private
> >> >> will likely get ignored or forwarded to a public forum with no further
> >> >> warning.

> >> > --
> >> > Jean-Baptiste M. "JBQ" Queru
> >> > Android Engineer, Google.

> >> > Questions sent directly to me that have no reason for being private
> >> > will likely get ignored or forwarded to a public forum with no further
> >> > warning.

> >> --
> >> Jean-Baptiste M. "JBQ" Queru
> >> Android Engineer, Google.

> >> Questions sent directly to me that have no reason for being private
> >> will likely get ignored or forwarded to a public forum with no further
> >> warning.

> --
> Jean-Baptiste M. "JBQ" Queru
> Android Engineer, Google.

> Questions sent directly to me that have no reason for being private
> will likely get ignored or forwarded to a public forum with no further
> warning.