JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, 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.
Thanks,
JBQ
2011/9/8 József Király <foni...@gmail.com>:
We have plans to make sure that the GPL source files for Gingerbread
and Honeycomb can be distributed independently, in case we decide to
make releases beyond 2.3.5 and 3.2.
JBQ
--
JBQ
--
Does that mean that https://github.com/android is not an official mirror?
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
_The Busy Coder's Guide to Android Development_ Version 3.6 Available!
JBQ
--
You have already made a release beyond 2.3.5, it seems my whole question has been avoided.
JBQ
JBQ
2011/9/12 József Király <foni...@gmail.com>:
JBQ
Github is the primary copy while they run gerrit on their own server.
JBQ
2011/9/12 József Király <foni...@gmail.com>:
JBQ
AFAIK on CM Gerrit is really Just a overview tool, and it manages the Github repos.
Just for the record: As far as I know Gerrit requires direct
filesystem access to its primary git repositories containing both the
committed and the proposed changes, so Cyanogen is probably running
Gerrit on its own server like AOSP does / did, and uses github as the
distribution mirror the same way AOSP used kernel.org.
So theoretically it should be possible to migrate to github for the
source mirrors. However, after the kernel.org fiasco, I would totally
understand if Google wanted to keep the whole infrastructure inhouse.
Best Regards,
Gergely
2011/9/12 Jean-Baptiste Queru <j...@android.com>:
--
Kis Gergely
ügyvezető / CEO
MattaKis Consulting
Email: gerge...@mattakis.com
Web: http://www.mattakis.com
Phone: +36 70 408 1723
Fax: +36 27 998 622
--
Kis Gergely
ügyvezető / CEO
MattaKis Consulting
Email: gerge...@mattakis.com
Web: http://www.mattakis.com
Phone: +36 70 408 1723
Fax: +36 27 998 622
We're working on getting back online, and we'll let everyone know as
soon as we have something that people can use.
JBQ
Joke aside, we're working on it, but I can't provide any additional
details at the moment.
JBQ
JBQ
2011/10/7 József Király <foni...@gmail.com>:
JBQ
You're looking for Software Engineering Intern position for Mountain
View (listed under North America). I can't possibly make any promise
that there'd be an internship position open in my team, or that you'd
get it, but if you apply be sure to mention AOSP in whichever part of
the process would be the most appropriate (I don't now what that would
be).
JBQ
http://groups.google.com/group/android-building/msg/c73c14f9b0dcd15a
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
_Android Programming Tutorials_ Version 4.0 Available!
Our next step is now to get Gerrit back online, and there's nothing
specific to announce on that other than "we're working on it".
JBQ
AOSP is back. (http://groups.google.com/group/android-building/msg/c73c14f9b0dcd15a)
But it would seem Gerrit is not able to use yet. manifest.xml file
doesn't have a proper review uri.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="aosp"
fetch=".." />
<default revision="master"
remote="aosp"
sync-j="4" />
Regards,
Leonardo YongUk KIM
That being said, all the releases mentioned on
http://source.android.com/source/build-numbers.html are there, along
with the froyo, gingerbread and master branches.
JBQ
JBQ
--
Gerrit is now self-hosted, and the Gerrit engineers have been using it
as their day-to-day tool. At this point, they're in the process of
hunting the last few bugs, and (like you know) once you're down to a
handful of bugs it's very hard to give any kind of precise estimates.
After we lost all the AOSP servers, the top priority was to get some
git hosting again, to restore the proper files there, and to release
ICS. That took us into mid-November. Since then, the efforts on that
side have been focused on Gerrit, but it's really only been 6 weeks.
AOSP will have a Gerrit server again, hopefully soon, but there's
simply no way to give any kind of reliable estimate at this point.
JBQ
--
Software doesn't write itself. Worse, it doesn't debug itself. Gerrit is now self-hosted, and the Gerrit engineers have been using it as their day-to-day tool. At this point, they're in the process of hunting the last few bugs, and (like you know) once you're down to a handful of bugs it's very hard to give any kind of precise estimates. After we lost all the AOSP servers, the top priority was to get some git hosting again, to restore the proper files there, and to release ICS. That took us into mid-November. Since then, the efforts on that side have been focused on Gerrit, but it's really only been 6 weeks. AOSP will have a Gerrit server again, hopefully soon, but there's simply no way to give any kind of reliable estimate at this point. JBQ
-- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com
I am surprised though that the decision to not Open-Source Honeycomb
is still not understood after 10 months. Google has explained it many
times already, it's really simple: Honeycomb wasn't shippable on
phones as-is. The apps had a mix-and-match of the Gingerbread look and
the Honeycomb look, the system UI for phones was missing elements
that'd have been necessary for compatibility (e.g. the action bar). We
release code when it's ready for all OEMs to use and ship, and
Honeycomb never was. That's it. There's no longer explanation, that's
really all there is to it.
I hope we see you contribute again once Gerrit is running again, but I
understand that life flows and will take contributors to other places.
Android and AOSP are still here and they're not going away.
JBQ
--
The whole Android platform code has been available on googlesource.com
since mid-October, and the git downtime was only about 7 weeks (i.e. 4
releases). Please ask on android-platform which exact code you're
looking for and I'll try to help you find it. As far as I know I've
restored everything all the way back to donut.
Would you feel better if I gave you an estimate from /dev/random?
I don't need to tell you that Android isn't dead, you can see it for
yourself. Look at the number of changes from Gingerbread to ICS to get
convinced.
JBQ
--
We're hitting one such bug on Gerrit. The development phase completed
on schedule a while ago, but there's a very annoying bug that makes
Gerrit impossible to deploy in public at the moment and that we can't
manage to pinpoint. There's simply no way to provide any estimate for
a bugfix for such a bug. No amount of wanting that bug fixed today or
yesterday or 3 months ago will fix that bug.
Google is not trying to hide anything here, we're just as frustrated
with the current situation as everyone else.
JBQ
--
As for Gerrit; I'd rather see things done right than done to a timetable.
Al.
--
T: @alsutton W: www.funkyandroid.com
The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.
I AM the manager. Unfortunately we have no ETA to provide.
It is your prerogative to disbelieve what we (and specifically I and JBQ) have said to date, of course. But we aren't going to give half-baked estimates that would be misleading.
I apologize for the continued downtime of the AOSP gerrit instance. It will be restored as soon as we have it working reasonably bug-free.
- Dan
JBQ
--