I've just created an eclair branch in AOSP, which contains the code
that many people have been waiting for.
What's in that branch? It's basically a snapshot of part of Google's
internal eclair tree, a little bit more recent than the build that was
used in Droid. It's not the exact source for Droid and is not ready to
ship on a consumer device.
Caveats:
-There's no change history. Google is planning to eventually make the
change history available, but at the moment the history contains some
things that can't be open-sourced, and making a snapshot was the
fastest way to deal with those.
-It's a partial tree. We'll be open-sourcing more of eclair over time,
but we figured it would make more sense to open-source part of it now
instead of waiting until everything was in place.
-It doesn't build for ADP1 or ION/ADP2. We're working with the various
companies involved to try to resolve this issue, but we preferred to
open-source the code in its current state instead of waiting for a
solution on the hardware side.
-It's not currently merged in the master tree. I'm working on it, but
I wanted to get something out before the week-end. Please be patient.
I'll try to complete it as quickly as I can.
-It doesn't currently contain the AOSP-specific files (build
configurations, etc...). They'll come back.
-Calendar is broken. I have a fix that I will release along with the
master tree.
Thanks for your hard work, and putting up with all of us complaining up
until the source was released :P
On Nov 13, 2009 6:57 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
I've just created an eclair branch in AOSP, which contains the code
that many people have been waiting for.
What's in that branch? It's basically a snapshot of part of Google's
internal eclair tree, a little bit more recent than the build that was
used in Droid. It's not the exact source for Droid and is not ready to
ship on a consumer device.
Caveats:
-There's no change history. Google is planning to eventually make the
change history available, but at the moment the history contains some
things that can't be open-sourced, and making a snapshot was the
fastest way to deal with those.
-It's a partial tree. We'll be open-sourcing more of eclair over time,
but we figured it would make more sense to open-source part of it now
instead of waiting until everything was in place.
-It doesn't build for ADP1 or ION/ADP2. We're working with the various
companies involved to try to resolve this issue, but we preferred to
open-source the code in its current state instead of waiting for a
solution on the hardware side.
-It's not currently merged in the master tree. I'm working on it, but
I wanted to get something out before the week-end. Please be patient.
I'll try to complete it as quickly as I can.
-It doesn't currently contain the AOSP-specific files (build
configurations, etc...). They'll come back.
-Calendar is broken. I have a fix that I will release along with the
master tree.
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.
--
You received this message because you are subscribed to the Google Groups
"android-platform" group.
To post to this group, send email to android-platform@googlegroups.com.
To unsubscribe from this group, send email to
android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
.
For more options, visit this group at
http://groups.google.com/group/android-platform?hl=.
On Fri, Nov 13, 2009 at 9:00 PM, Ryan Gardner <ryeb...@gmail.com> wrote:
> JBQ == the man.
> Thanks for your hard work, and putting up with all of us complaining up
> until the source was released :P
> On Nov 13, 2009 6:57 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
> I've just created an eclair branch in AOSP, which contains the code
> that many people have been waiting for.
> What's in that branch? It's basically a snapshot of part of Google's
> internal eclair tree, a little bit more recent than the build that was
> used in Droid. It's not the exact source for Droid and is not ready to
> ship on a consumer device.
> Caveats:
> -There's no change history. Google is planning to eventually make the
> change history available, but at the moment the history contains some
> things that can't be open-sourced, and making a snapshot was the
> fastest way to deal with those.
> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> but we figured it would make more sense to open-source part of it now
> instead of waiting until everything was in place.
> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> companies involved to try to resolve this issue, but we preferred to
> open-source the code in its current state instead of waiting for a
> solution on the hardware side.
> -It's not currently merged in the master tree. I'm working on it, but
> I wanted to get something out before the week-end. Please be patient.
> I'll try to complete it as quickly as I can.
> -It doesn't currently contain the AOSP-specific files (build
> configurations, etc...). They'll come back.
> -Calendar is broken. I have a fix that I will release along with the
> master tree.
> 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.
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=.
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=.
> I've just created an eclair branch in AOSP, which contains the code
> that many people have been waiting for.
> What's in that branch? It's basically a snapshot of part of Google's
> internal eclair tree, a little bit more recent than the build that was
> used in Droid. It's not the exact source for Droid and is not ready to
> ship on a consumer device.
> Caveats:
> -There's no change history. Google is planning to eventually make the
> change history available, but at the moment the history contains some
> things that can't be open-sourced, and making a snapshot was the
> fastest way to deal with those.
> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> but we figured it would make more sense to open-source part of it now
> instead of waiting until everything was in place.
> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> companies involved to try to resolve this issue, but we preferred to
> open-source the code in its current state instead of waiting for a
> solution on the hardware side.
> -It's not currently merged in the master tree. I'm working on it, but
> I wanted to get something out before the week-end. Please be patient.
> I'll try to complete it as quickly as I can.
> -It doesn't currently contain the AOSP-specific files (build
> configurations, etc...). They'll come back.
> -Calendar is broken. I have a fix that I will release along with the
> master tree.
> 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.
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=.
Actually, you really want to thank the entire Android team. They wrote
the code, I just released it, and while releasing Eclair gave me a
very busy week, creating it gave them some very busy months, so I only
deserve a fraction of a percent of the credit.
On Fri, Nov 13, 2009 at 6:00 PM, Ryan Gardner <ryeb...@gmail.com> wrote:
> JBQ == the man.
> Thanks for your hard work, and putting up with all of us complaining up
> until the source was released :P
> On Nov 13, 2009 6:57 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
> I've just created an eclair branch in AOSP, which contains the code
> that many people have been waiting for.
> What's in that branch? It's basically a snapshot of part of Google's
> internal eclair tree, a little bit more recent than the build that was
> used in Droid. It's not the exact source for Droid and is not ready to
> ship on a consumer device.
> Caveats:
> -There's no change history. Google is planning to eventually make the
> change history available, but at the moment the history contains some
> things that can't be open-sourced, and making a snapshot was the
> fastest way to deal with those.
> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> but we figured it would make more sense to open-source part of it now
> instead of waiting until everything was in place.
> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> companies involved to try to resolve this issue, but we preferred to
> open-source the code in its current state instead of waiting for a
> solution on the hardware side.
> -It's not currently merged in the master tree. I'm working on it, but
> I wanted to get something out before the week-end. Please be patient.
> I'll try to complete it as quickly as I can.
> -It doesn't currently contain the AOSP-specific files (build
> configurations, etc...). They'll come back.
> -Calendar is broken. I have a fix that I will release along with the
> master tree.
> 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.
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platform+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=.
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platform+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=.
Jean-Baptiste Queru wrote:
> Actually, you really want to thank the entire Android team. They wrote
> the code, I just released it, and while releasing Eclair gave me a
> very busy week, creating it gave them some very busy months, so I only
> deserve a fraction of a percent of the credit.
> JBQ
I'm sorry for being a bit blunt, but that's not the way I see it.
Android as just another phone OS is just as interesting to me as Symbian, iPhone or Windows Mo (i.e. - not very much). If that's all Android is, I'd just be reviving my Free Runner and be working on OpenMoko right now. The thing that makes Android interesting is it's open source. This means that, as far as I'm concerned, your weekend's is, by far, more important work than the rest of the months spent producing proprietary, closed software.
Put another way - I'm willing (and anxious) to help with the month's worth of hard work, but without your hard work, I wouldn't even be able to be a bystander.
> Jean-Baptiste Queru wrote:
> > Actually, you really want to thank the entire Android team. They wrote
> > the code, I just released it, and while releasing Eclair gave me a
> > very busy week, creating it gave them some very busy months, so I only
> > deserve a fraction of a percent of the credit.
> > JBQ
> I'm sorry for being a bit blunt, but that's not the way I see it.
> Android as just another phone OS is just as interesting to me as
> Symbian, iPhone or Windows Mo (i.e. - not very much). If that's all
> Android is, I'd just be reviving my Free Runner and be working on
> OpenMoko right now. The thing that makes Android interesting is it's
> open source. This means that, as far as I'm concerned, your weekend's
> is, by far, more important work than the rest of the months spent
> producing proprietary, closed software.
> Put another way - I'm willing (and anxious) to help with the month's
> worth of hard work, but without your hard work, I wouldn't even be able
> to be a bystander.
I just wanted to say thank you. This is such fantastic news and I hope
you know that your hard work is so very appreciated. This is something
that the entire Android team at Google (and all of the members of the
Open Handset Alliance) should be extremely proud of.
Once again, thanks. I am very excited.
On Nov 13, 6:57 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> I've just created an eclair branch in AOSP, which contains the code
> that many people have been waiting for.
> What's in that branch? It's basically a snapshot of part of Google's
> internal eclair tree, a little bit more recent than the build that was
> used in Droid. It's not the exact source for Droid and is not ready to
> ship on a consumer device.
> Caveats:
> -There's no change history. Google is planning to eventually make the
> change history available, but at the moment the history contains some
> things that can't be open-sourced, and making a snapshot was the
> fastest way to deal with those.
> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> but we figured it would make more sense to open-source part of it now
> instead of waiting until everything was in place.
> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> companies involved to try to resolve this issue, but we preferred to
> open-source the code in its current state instead of waiting for a
> solution on the hardware side.
> -It's not currently merged in the master tree. I'm working on it, but
> I wanted to get something out before the week-end. Please be patient.
> I'll try to complete it as quickly as I can.
> -It doesn't currently contain the AOSP-specific files (build
> configurations, etc...). They'll come back.
> -Calendar is broken. I have a fix that I will release along with the
> master tree.
> 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.
> Actually, you really want to thank the entire Android team. They wrote
> the code, I just released it, and while releasing Eclair gave me a
> very busy week, creating it gave them some very busy months, so I only
> deserve a fraction of a percent of the credit.
> JBQ
> On Fri, Nov 13, 2009 at 6:00 PM, Ryan Gardner <ryeb...@gmail.com> wrote:
> > JBQ == the man.
> > Thanks for your hard work, and putting up with all of us complaining up
> > until the source was released :P
> > On Nov 13, 2009 6:57 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
> > I've just created an eclair branch in AOSP, which contains the code
> > that many people have been waiting for.
> > What's in that branch? It's basically a snapshot of part of Google's
> > internal eclair tree, a little bit more recent than the build that was
> > used in Droid. It's not the exact source for Droid and is not ready to
> > ship on a consumer device.
> > Caveats:
> > -There's no change history. Google is planning to eventually make the
> > change history available, but at the moment the history contains some
> > things that can't be open-sourced, and making a snapshot was the
> > fastest way to deal with those.
> > -It's a partial tree. We'll be open-sourcing more of eclair over time,
> > but we figured it would make more sense to open-source part of it now
> > instead of waiting until everything was in place.
> > -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> > companies involved to try to resolve this issue, but we preferred to
> > open-source the code in its current state instead of waiting for a
> > solution on the hardware side.
> > -It's not currently merged in the master tree. I'm working on it, but
> > I wanted to get something out before the week-end. Please be patient.
> > I'll try to complete it as quickly as I can.
> > -It doesn't currently contain the AOSP-specific files (build
> > configurations, etc...). They'll come back.
> > -Calendar is broken. I have a fix that I will release along with the
> > master tree.
> > 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.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "android-platform" group.
> > To post to this group, send email to android-platform@googlegroups.com.
> > To unsubscribe from this group, send email to
> > android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/android-platform?hl=.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "android-platform" group.
> > To post to this group, send email to android-platform@googlegroups.com.
> > To unsubscribe from this group, send email to
> > android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/android-platform?hl=.
> 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.
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=.
> Actually, you really want to thank the entire Android team. They wrote
> the code, I just released it, and while releasing Eclair gave me a
> very busy week, creating it gave them some very busy months, so I only
> deserve a fraction of a percent of the credit.
> JBQ
> I'm sorry for being a bit blunt, but that's not the way I see it.
> Android as just another phone OS is just as interesting to me as Symbian,
> iPhone or Windows Mo (i.e. - not very much). If that's all Android is, I'd
> just be reviving my Free Runner and be working on OpenMoko right now. The
> thing that makes Android interesting is it's open source. This means that,
> as far as I'm concerned, your weekend's is, by far, more important work than
> the rest of the months spent producing proprietary, closed software.
> Put another way - I'm willing (and anxious) to help with the month's worth
> of hard work, but without your hard work, I wouldn't even be able to be a
> bystander.
> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platform+unsubscribe@googlegroups.com<android-platform%2Bunsubscrib e@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=.
> Thanks. I did
> * repo sync
> * lunch generic-eng
> * make -j4
> and run the emulator. Why it still said I am using 1.6.
> Can you please tell me what am I missing? I create my repo using 'repo
> init -u git://android.git.kernel.org/platform/manifest.git'
> Thank you.
> On Nov 13, 9:48 pm, Shachar Shemesh <shac...@shemesh.biz> wrote:
> > Jean-Baptiste Queru wrote:
> > > Actually, you really want to thank the entire Android team. They wrote
> > > the code, I just released it, and while releasing Eclair gave me a
> > > very busy week, creating it gave them some very busy months, so I only
> > > deserve a fraction of a percent of the credit.
> > > JBQ
> > I'm sorry for being a bit blunt, but that's not the way I see it.
> > Android as just another phone OS is just as interesting to me as
> > Symbian, iPhone or Windows Mo (i.e. - not very much). If that's all
> > Android is, I'd just be reviving my Free Runner and be working on
> > OpenMoko right now. The thing that makes Android interesting is it's
> > open source. This means that, as far as I'm concerned, your weekend's
> > is, by far, more important work than the rest of the months spent
> > producing proprietary, closed software.
> > Put another way - I'm willing (and anxious) to help with the month's
> > worth of hard work, but without your hard work, I wouldn't even be able
> > to be a bystander.
Essentially, yes. From this point, all device manufacturers can start
working on getting Eclair working on their new or existing devices, if
that's their strategy. Really, though, it's up to them, and the
Android Open-Source Project can't force anyone to use that new code.
JBQ
On Fri, Nov 13, 2009 at 11:53 PM, Gerd Steinwender <g.ste...@gmail.com> wrote:
> does this mean that from now on it is on samsung to make an update to
> 2.0 for their galaxy handset?
> --
> You received this message because you are subscribed to the Google Groups "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-platform?hl=.
I haven't merged eclair into master yet, so master still contains a
variant of 1.6, and master is the default branch. Give me a few days
and that'll get resolved.
On Sat, Nov 14, 2009 at 1:06 AM, n179911 <n179...@gmail.com> wrote:
> Thanks. I did
> * repo sync
> * lunch generic-eng
> * make -j4
> and run the emulator. Why it still said I am using 1.6.
> Can you please tell me what am I missing? I create my repo using 'repo
> init -u git://android.git.kernel.org/platform/manifest.git'
> Thank you.
> On Nov 13, 9:48 pm, Shachar Shemesh <shac...@shemesh.biz> wrote:
>> Jean-Baptiste Queru wrote:
>> > Actually, you really want to thank the entire Android team. They wrote
>> > the code, I just released it, and while releasing Eclair gave me a
>> > very busy week, creating it gave them some very busy months, so I only
>> > deserve a fraction of a percent of the credit.
>> > JBQ
>> I'm sorry for being a bit blunt, but that's not the way I see it.
>> Android as just another phone OS is just as interesting to me as
>> Symbian, iPhone or Windows Mo (i.e. - not very much). If that's all
>> Android is, I'd just be reviving my Free Runner and be working on
>> OpenMoko right now. The thing that makes Android interesting is it's
>> open source. This means that, as far as I'm concerned, your weekend's
>> is, by far, more important work than the rest of the months spent
>> producing proprietary, closed software.
>> Put another way - I'm willing (and anxious) to help with the month's
>> worth of hard work, but without your hard work, I wouldn't even be able
>> to be a bystander.
> You received this message because you are subscribed to the Google Groups "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-platform?hl=.
Big thanks to everyone who has worked to make eclair the most amazing
build of Android yet and also a big thanks to JBQ for dropping it into
the AOSP :-)
I think its now time for HTC to go be very busy!
On Nov 14, 1:57 am, Jean-Baptiste Queru <j...@android.com> wrote:
> I've just created an eclair branch in AOSP, which contains the code
> that many people have been waiting for.
> What's in that branch? It's basically a snapshot of part of Google's
> internal eclair tree, a little bit more recent than the build that was
> used in Droid. It's not the exact source for Droid and is not ready to
> ship on a consumer device.
> Caveats:
> -There's no change history. Google is planning to eventually make the
> change history available, but at the moment the history contains some
> things that can't be open-sourced, and making a snapshot was the
> fastest way to deal with those.
> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> but we figured it would make more sense to open-source part of it now
> instead of waiting until everything was in place.
> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> companies involved to try to resolve this issue, but we preferred to
> open-source the code in its current state instead of waiting for a
> solution on the hardware side.
> -It's not currently merged in the master tree. I'm working on it, but
> I wanted to get something out before the week-end. Please be patient.
> I'll try to complete it as quickly as I can.
> -It doesn't currently contain the AOSP-specific files (build
> configurations, etc...). They'll come back.
> -Calendar is broken. I have a fix that I will release along with the
> master tree.
> 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.
> I've just created an eclair branch in AOSP, which contains the code
> that many people have been waiting for.
> What's in that branch? It's basically a snapshot of part of Google's
> internal eclair tree, a little bit more recent than the build that was
> used in Droid. It's not the exact source for Droid and is not ready to
> ship on a consumer device.
> Caveats:
> -There's no change history. Google is planning to eventually make the
> change history available, but at the moment the history contains some
> things that can't be open-sourced, and making a snapshot was the
> fastest way to deal with those.
> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> but we figured it would make more sense to open-source part of it now
> instead of waiting until everything was in place.
> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> companies involved to try to resolve this issue, but we preferred to
> open-source the code in its current state instead of waiting for a
> solution on the hardware side.
> -It's not currently merged in the master tree. I'm working on it, but
> I wanted to get something out before the week-end. Please be patient.
> I'll try to complete it as quickly as I can.
> -It doesn't currently contain the AOSP-specific files (build
> configurations, etc...). They'll come back.
> -Calendar is broken. I have a fix that I will release along with the
> master tree.
> 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.
On Sat, Nov 14, 2009 at 7:02 AM, Billy Cui <billy...@gmail.com> wrote:
> Great job, actually I have check them out and make some of them, but
> find it fail to run in emulator, said it require development platform.
> So keep going, waiting for your further code.
> Any timeline about the total release of the eclair code?
> On Nov 14, 9:57 am, Jean-Baptiste Queru <j...@android.com> wrote:
>> I've just created an eclair branch in AOSP, which contains the code
>> that many people have been waiting for.
>> What's in that branch? It's basically a snapshot of part of Google's
>> internal eclair tree, a little bit more recent than the build that was
>> used in Droid. It's not the exact source for Droid and is not ready to
>> ship on a consumer device.
>> Caveats:
>> -There's no change history. Google is planning to eventually make the
>> change history available, but at the moment the history contains some
>> things that can't be open-sourced, and making a snapshot was the
>> fastest way to deal with those.
>> -It's a partial tree. We'll be open-sourcing more of eclair over time,
>> but we figured it would make more sense to open-source part of it now
>> instead of waiting until everything was in place.
>> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
>> companies involved to try to resolve this issue, but we preferred to
>> open-source the code in its current state instead of waiting for a
>> solution on the hardware side.
>> -It's not currently merged in the master tree. I'm working on it, but
>> I wanted to get something out before the week-end. Please be patient.
>> I'll try to complete it as quickly as I can.
>> -It doesn't currently contain the AOSP-specific files (build
>> configurations, etc...). They'll come back.
>> -Calendar is broken. I have a fix that I will release along with the
>> master tree.
>> 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.
> --
> You received this message because you are subscribed to the Google Groups "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-platform?hl=.
> On Sat, Nov 14, 2009 at 7:02 AM, Billy Cui <billy...@gmail.com> wrote:
> > Great job, actually I have check them out and make some of them, but
> > find it fail to run in emulator, said it require development platform.
> > So keep going, waiting for your further code.
> > Any timeline about the total release of the eclair code?
> > On Nov 14, 9:57 am, Jean-Baptiste Queru <j...@android.com> wrote:
> >> I've just created an eclair branch in AOSP, which contains the code
> >> that many people have been waiting for.
> >> What's in that branch? It's basically a snapshot of part of Google's
> >> internal eclair tree, a little bit more recent than the build that was
> >> used in Droid. It's not the exact source for Droid and is not ready to
> >> ship on a consumer device.
> >> Caveats:
> >> -There's no change history. Google is planning to eventually make the
> >> change history available, but at the moment the history contains some
> >> things that can't be open-sourced, and making a snapshot was the
> >> fastest way to deal with those.
> >> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> >> but we figured it would make more sense to open-source part of it now
> >> instead of waiting until everything was in place.
> >> -It doesn't build for ADP1 or ION/ADP2. We're working with the various
> >> companies involved to try to resolve this issue, but we preferred to
> >> open-source the code in its current state instead of waiting for a
> >> solution on the hardware side.
> >> -It's not currently merged in the master tree. I'm working on it, but
> >> I wanted to get something out before the week-end. Please be patient.
> >> I'll try to complete it as quickly as I can.
> >> -It doesn't currently contain the AOSP-specific files (build
> >> configurations, etc...). They'll come back.
> >> -Calendar is broken. I have a fix that I will release along with the
> >> master tree.
> >> 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.
> > --
> > You received this message because you are subscribed to the Google Groups "android-platform" group.
> > To post to this group, send email to android-platform@googlegroups.com.
> > To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/android-platform?hl=.
> 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.
> I haven't merged eclair into master yet, so master still contains a
> variant of 1.6, and master is the default branch. Give me a few days
> and that'll get resolved.
> JBQ
> On Sat, Nov 14, 2009 at 1:06 AM, n179911 <n179...@gmail.com> wrote:
> > Thanks. I did
> > * repo sync
> > * lunch generic-eng
> > * make -j4
> > and run the emulator. Why it still said I am using 1.6.
> > Can you please tell me what am I missing? I create my repo using 'repo
> > init -u git://android.git.kernel.org/platform/manifest.git'
> > Thank you.
> > On Nov 13, 9:48 pm, Shachar Shemesh <shac...@shemesh.biz> wrote:
> >> Jean-Baptiste Queru wrote:
> >> > Actually, you really want to thank the entire Android team. They wrote
> >> > the code, I just released it, and while releasing Eclair gave me a
> >> > very busy week, creating it gave them some very busy months, so I only
> >> > deserve a fraction of a percent of the credit.
> >> > JBQ
> >> I'm sorry for being a bit blunt, but that's not the way I see it.
> >> Android as just another phone OS is just as interesting to me as
> >> Symbian, iPhone or Windows Mo (i.e. - not very much). If that's all
> >> Android is, I'd just be reviving my Free Runner and be working on
> >> OpenMoko right now. The thing that makes Android interesting is it's
> >> open source. This means that, as far as I'm concerned, your weekend's
> >> is, by far, more important work than the rest of the months spent
> >> producing proprietary, closed software.
> >> Put another way - I'm willing (and anxious) to help with the month's
> >> worth of hard work, but without your hard work, I wouldn't even be able
> >> to be a bystander.
> > You received this message because you are subscribed to the Google Groups "android-platform" group.
> > To post to this group, send email to android-platform@googlegroups.com.
> > To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/android-platform?hl=.
> 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.
On Fri, Nov 13, 2009 at 9:48 PM, Shachar Shemesh <shac...@shemesh.biz>wrote:
> Android as just another phone OS is just as interesting to me as Symbian,
> iPhone or Windows Mo (i.e. - not very much). If that's all Android is, I'd
> just be reviving my Free Runner and be working on OpenMoko right now. The
> thing that makes Android interesting is it's open source. This means that,
> as far as I'm concerned, your weekend's is, by far, more important work than
> the rest of the months spent producing proprietary, closed software.
Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails. All such
questions should be posted on public forums, where I and others can see and
answer them.
The way to get there is to go to the frameworks/base page
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=summary and scroll down to the "heads" section. The first one on the list is
eclair, since it's the most recently updated. Click the "tree" link
next to it, and you can browse the eclair tree for frameworks/base.
Repeat approximately 130 times to do it in the other projects.
Note, if you prefer to get the source code locally, use repo init -u
git://android.git.kernel.org/platform/manifest.git -b eclair
Sorry if I didn't clarify those earlier - I'm used to using those
tools so much and I've focused so much of my energy on just getting
the source out that I failed to take a few steps back and I kinda
forgot that not everyone spends 12+ hours a day using those tools.
On Sat, Nov 14, 2009 at 9:55 AM, joebowbeer <joe.bowb...@gmail.com> wrote:
> For those browsing sources who (like me) hadn't figured this out yet,
> hb=eclair is key.
> A link, for example, to the ContactsContract source:
> On Nov 14, 5:08 am, Jean-Baptiste Queru <j...@android.com> wrote:
>> 'repo init -u git://android.git.kernel.org/platform/manifest.git -b eclair'
>> I haven't merged eclair into master yet, so master still contains a
>> variant of 1.6, and master is the default branch. Give me a few days
>> and that'll get resolved.
>> JBQ
>> On Sat, Nov 14, 2009 at 1:06 AM, n179911 <n179...@gmail.com> wrote:
>> > Thanks. I did
>> > * repo sync
>> > * lunch generic-eng
>> > * make -j4
>> > and run the emulator. Why it still said I am using 1.6.
>> > Can you please tell me what am I missing? I create my repo using 'repo
>> > init -u git://android.git.kernel.org/platform/manifest.git'
>> > Thank you.
>> > On Nov 13, 9:48 pm, Shachar Shemesh <shac...@shemesh.biz> wrote:
>> >> Jean-Baptiste Queru wrote:
>> >> > Actually, you really want to thank the entire Android team. They wrote
>> >> > the code, I just released it, and while releasing Eclair gave me a
>> >> > very busy week, creating it gave them some very busy months, so I only
>> >> > deserve a fraction of a percent of the credit.
>> >> > JBQ
>> >> I'm sorry for being a bit blunt, but that's not the way I see it.
>> >> Android as just another phone OS is just as interesting to me as
>> >> Symbian, iPhone or Windows Mo (i.e. - not very much). If that's all
>> >> Android is, I'd just be reviving my Free Runner and be working on
>> >> OpenMoko right now. The thing that makes Android interesting is it's
>> >> open source. This means that, as far as I'm concerned, your weekend's
>> >> is, by far, more important work than the rest of the months spent
>> >> producing proprietary, closed software.
>> >> Put another way - I'm willing (and anxious) to help with the month's
>> >> worth of hard work, but without your hard work, I wouldn't even be able
>> >> to be a bystander.
>> > You received this message because you are subscribed to the Google Groups "android-platform" group.
>> > To post to this group, send email to android-platform@googlegroups.com.
>> > To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.
>> > For more options, visit this group athttp://groups.google.com/group/android-platform?hl=.
>> 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.
> --
> You received this message because you are subscribed to the Google Groups "android-platform" group.
> To post to this group, send email to android-platform@googlegroups.com.
> To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-platform?hl=.
This is great news, thank you all (JBQ and the countless other
developers) for your hard work.
We discussed about branches a few weeks back on the list.
I would like to make a proposal regarding the merging to master. I
think it would make sense to hold off the merge to master until the
necessary closed source binaries for ADP1 and/or ADP2 are available.
This way the master branch would always be usable to build software
for the "official" Android platform development devices.
If you think that it is more important to get the new code into master
even at the cost of breaking the device builds, then I would like to
propose to create an "oldmaster" branch, or at least a frozen repo
manifest which can be used to build for devices, while the vendors are
releasing the necessary closed-source binaries for the new version.
What do you think?
On Sat, Nov 14, 2009 at 2:57 AM, Jean-Baptiste Queru <j...@android.com> wrote:
> -It's a partial tree. We'll be open-sourcing more of eclair over time,
> but we figured it would make more sense to open-source part of it now
> instead of waiting until everything was in place.
Could you give us a bit more details what is missing?
Just saw that you are going to do just what I was proposing...sorry
for the noise.
On Sat, Nov 14, 2009 at 8:16 PM, Gergely Kis <gergely....@gmail.com> wrote:
> Hi,
> This is great news, thank you all (JBQ and the countless other
> developers) for your hard work.
> We discussed about branches a few weeks back on the list.
> I would like to make a proposal regarding the merging to master. I
> think it would make sense to hold off the merge to master until the
> necessary closed source binaries for ADP1 and/or ADP2 are available.
> This way the master branch would always be usable to build software
> for the "official" Android platform development devices.
On Sat, Nov 14, 2009 at 10:07 AM, Jean-Baptiste Queru <j...@android.com> wrote:
> That is correct.
> The way to get there is to go to the frameworks/base page
> http://android.git.kernel.org/?p=platform/frameworks/base.git;a=summary > and scroll down to the "heads" section. The first one on the list is
> eclair, since it's the most recently updated. Click the "tree" link
> next to it, and you can browse the eclair tree for frameworks/base.
> Repeat approximately 130 times to do it in the other projects.
until someone with free time comes up with a repo-web (wrapped around
the git-web) :-)
Its really great to see eclair in AOSP finally. Thank you JBQ!
Do you see further big updates to eclair branch coming later, or is it
mostly complete except for future patches?
