I expect that future updates won't be huge (definitely not as big as
going from 1.x to eclair), but that they won't be tiny either (i.e.
larger than upgrading from 1.5r1 to 1.5r4). I expect that they'll be
more about breadth (i.e. packages that aren't currently open-sourced,
e.g. some settings apps that are currently missing) than depth.
i.e. if you're an OEM working on a device currently running 1.5 or
1.6, getting the current eclair up-and-running will get you most of
the way "there" in terms of the port and will cut your schedule
significantly toward being able to upgrade your users' devices, but
you need to expect that there'll still be some additional work,
including/especially at the UI level.
On Sat, Nov 14, 2009 at 11:41 AM, Jey Michael <jey.mich...@gmail.com> wrote:
> 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?
> -Jey
> --
> 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=.
Dianne Hackborn wrote:
> On Fri, Nov 13, 2009 at 9:48 PM, Shachar Shemesh <shac...@shemesh.biz > <mailto: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.
> We love you too!
Please don't take this personally, but what you do on your day job is, at best, invisible to me. At worst, it directly conflicts with what I'm trying to do on your platform (and the fact there are no quotes around the "your" signifies the problem more than anything else). I'm not saying you aren't doing a heck of a job. I'm saying that until JBQ does his stuff, I don't know what kind of a job you do, and then I get so many changes at once, it's really difficult to measure how good your job is.
So, sorry, yes, I think his job is, at least for me, much more important.
The fact that you're using Android even though there are other phone
platforms/projects with vastly more open developing processes
(OpenMoko, Replicant, OpenAndroidAlliance, just to name a few) should
be a strong indication of the quality and value of Dianne's work (and
of the rest of the Android team).
If I had been the only person working on Android since the original
open-source release, all you'd have seen since then would be about
adding support for redirects and randomized exponential backoff in the
download manager, which isn't that exciting.
I wouldn't even have a job if Dianne and the rest of the Android team
weren't there, since there'd be no Android code to release in the
first place.
On Sat, Nov 14, 2009 at 12:21 PM, Shachar Shemesh <shac...@shemesh.biz> wrote:
> Dianne Hackborn wrote:
> 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.
> We love you too!
> Please don't take this personally, but what you do on your day job is, at
> best, invisible to me. At worst, it directly conflicts with what I'm trying
> to do on your platform (and the fact there are no quotes around the "your"
> signifies the problem more than anything else). I'm not saying you aren't
> doing a heck of a job. I'm saying that until JBQ does his stuff, I don't
> know what kind of a job you do, and then I get so many changes at once, it's
> really difficult to measure how good your job is.
> So, sorry, yes, I think his job is, at least for me, much more important.
> 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=.
> The fact that you're using Android even though there are other phone
> platforms/projects with vastly more open developing processes
> (OpenMoko, Replicant, OpenAndroidAlliance, just to name a few) should
> be a strong indication of the quality and value of Dianne's work (and
> of the rest of the Android team).
> If I had been the only person working on Android since the original
> open-source release, all you'd have seen since then would be about
> adding support for redirects and randomized exponential backoff in the
> download manager, which isn't that exciting.
> I wouldn't even have a job if Dianne and the rest of the Android team
> weren't there, since there'd be no Android code to release in the
> first place.
> JBQ
> On Sat, Nov 14, 2009 at 12:21 PM, Shachar Shemesh <shac...@shemesh.biz>
> wrote:
> > Dianne Hackborn wrote:
> > 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.
> > We love you too!
> > Please don't take this personally, but what you do on your day job is, at
> > best, invisible to me. At worst, it directly conflicts with what I'm
> trying
> > to do on your platform (and the fact there are no quotes around the
> "your"
> > signifies the problem more than anything else). I'm not saying you aren't
> > doing a heck of a job. I'm saying that until JBQ does his stuff, I don't
> > know what kind of a job you do, and then I get so many changes at once,
> it's
> > really difficult to measure how good your job is.
> > So, sorry, yes, I think his job is, at least for me, much more important.
> > 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=.
Along those lines, we (Google) do recognize that not having changelogs
for eclair is an issue, and we intend to make as many of them
available as possible as soon as possible. I can't promise that all of
them will be, and I can't give an exact timeline, but I'll work to
make it happen as reasonably as possible.
On Sat, Nov 14, 2009 at 12:54 PM, Fred Grott <fred.gr...@gmail.com> wrote:
> i know I see a lot of value in every Google engineers and OHA members work each time I read the commit logs and the source diffs
> Fred Grott
> Android Mobile Developer
> http://mobilebytes.wordpress.com/ > Chat Google Talk: fred.grott Skype: fred.grott
> Contact Me
> --- @ WiseStamp Signature. Get it now
> On Sat, Nov 14, 2009 at 2:50 PM, Jean-Baptiste Queru <j...@android.com> wrote:
>> The fact that you're using Android even though there are other phone
>> platforms/projects with vastly more open developing processes
>> (OpenMoko, Replicant, OpenAndroidAlliance, just to name a few) should
>> be a strong indication of the quality and value of Dianne's work (and
>> of the rest of the Android team).
>> If I had been the only person working on Android since the original
>> open-source release, all you'd have seen since then would be about
>> adding support for redirects and randomized exponential backoff in the
>> download manager, which isn't that exciting.
>> I wouldn't even have a job if Dianne and the rest of the Android team
>> weren't there, since there'd be no Android code to release in the
>> first place.
>> JBQ
>> On Sat, Nov 14, 2009 at 12:21 PM, Shachar Shemesh <shac...@shemesh.biz> wrote:
>> > Dianne Hackborn wrote:
>> > 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.
>> > We love you too!
>> > Please don't take this personally, but what you do on your day job is, at
>> > best, invisible to me. At worst, it directly conflicts with what I'm trying
>> > to do on your platform (and the fact there are no quotes around the "your"
>> > signifies the problem more than anything else). I'm not saying you aren't
>> > doing a heck of a job. I'm saying that until JBQ does his stuff, I don't
>> > know what kind of a job you do, and then I get so many changes at once, it's
>> > really difficult to measure how good your job is.
>> > So, sorry, yes, I think his job is, at least for me, much more important.
>> > 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=.
>> 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=.
On Fri, Nov 13, 2009 at 5: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.
> I've taken care of a few of the issues I had mentioned on Friday:
> -Eclairis now merged into master. Feel free to contribute.
> -Master contains additional fixes to make Calendar work, and also to
> make WebKit build properly.
> -I've added the AOSP-specific projects ineclair(and I've captured
> the evolution of the branch for future reference).
> The other issues remain open at this point. It looks like it might be
> possible to run master on ADP with partial functionality, that's on my
> list.
> JBQ
> On Fri, Nov 13, 2009 at 5:57 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> > I've just created aneclairbranch 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
> > internaleclairtree, 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 ofeclairover 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.
> 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 Tue, Nov 17, 2009 at 1:20 PM, RaviY <yend...@pv.com> wrote:
> Hi JBQ,
> Will there be some kind of a "tag" on the eclair branch, similar to
> what was on donut?
> Thanks,
> Ravi
> On Nov 15, 6:40 pm, Jean-Baptiste Queru <j...@android.com> wrote:
>> I've taken care of a few of the issues I had mentioned on Friday:
>> -Eclairis now merged into master. Feel free to contribute.
>> -Master contains additional fixes to make Calendar work, and also to
>> make WebKit build properly.
>> -I've added the AOSP-specific projects ineclair(and I've captured
>> the evolution of the branch for future reference).
>> The other issues remain open at this point. It looks like it might be
>> possible to run master on ADP with partial functionality, that's on my
>> list.
>> JBQ
>> On Fri, Nov 13, 2009 at 5:57 PM, Jean-Baptiste Queru <j...@android.com> wrote:
>> > I've just created aneclairbranch 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
>> > internaleclairtree, 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 ofeclairover 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.
>> 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=.
> There's no tag at this point, since the code as it has been released > isn't considered appropriate to ship as-is on a device.
> Once we reach a shippable state, there'll be a tag.
> JBQ
> On Tue, Nov 17, 2009 at 1:20 PM, RaviY <yend...@pv.com> wrote: > > Hi JBQ,
> > Will there be some kind of a "tag" on the eclair branch, similar to > > what was on donut?
> > Thanks, > > Ravi
> > On Nov 15, 6:40 pm, Jean-Baptiste Queru <j...@android.com> wrote: > >> I've taken care of a few of the issues I had mentioned on Friday:
> >> -Eclairis now merged into master. Feel free to contribute.
> >> -Master contains additional fixes to make Calendar work, and also to > >> make WebKit build properly.
> >> -I've added the AOSP-specific projects ineclair(and I've captured > >> the evolution of the branch for future reference).
> >> The other issues remain open at this point. It looks like it might be > >> possible to run master on ADP with partial functionality, that's on my > >> list.
> >> JBQ
> >> On Fri, Nov 13, 2009 at 5:57 PM, Jean-Baptiste Queru <j...@android.com> wrote: > >> > I've just created aneclairbranch 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 > >> > internaleclairtree, 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 ofeclairover 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.
> >> 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.
