Hello,

Here's update on the migration process:

1. I've made first pass thru updating wiki with new Android tree
location.
2. LEB-Panda currently doesn't build. That's because it turned out that
we have none tags at all in our existing (forked) Android components,
and manifest of leb-panda appears to refer to one of them.

My plan for today is to investigate and fix LEB-Panda breakage and
work towards setting up automated upstream sync process.

Few people asked how they can help with migration, and the answer is to
update their jobs on android-build.linaro.org, making sure they build
ok, updating their docs in wiki or elsewhere which may contain
references to old location, prodding colleagues to do the same ;-).

It would be nice if we focused on this for couple of days, as it will
be more complicated if we'll discover some serious issue later or just
will need to deal with corner cases again and again.


Thanks,
Paul


On Wed, 10 Aug 2011 20:31:11 +0300
Paul Sokolovsky <paul.sokolov...@linaro.org> wrote:

> [originally sent from wrong email, so not sure if got thru]
> 
> Hello,
> 
> Linaro Android codebase migration to Gerrit, which was announced at
> Linaro Connect, happened today. From now, Linaro Android is available
> via:
> 
> http://android.git.linaro.org/
> 
> Accompanied by Gerrit frontend at:
> 
> http://review.android.git.linaro.org/
> 
> It is recommended to perform a fresh checkout of the tree. To do that,
> run:
> 
> repo init -u git://android.git.linaro.org/platform/manifest.git \
>   -b <branch> \
>   -m <manifest>
> 
> <branch> and <manifest> are those you used before. E.g. 
> 
> repo init -u git://android.git.linaro.org/platform/manifest.git \
>   -b linaro_android_2.3.4 \
>   -m default.xml
> 
> 
> The official Linaro builds at https://android-build.linaro.org/ were
> converted to use new manifest location, and I'd like to ask other
> developers to convert their personal builds (I'm not trying to
> automate this so far, to make that everyone was in loop on what
> changed and how). To update, just change in a build config:
> 
> MANIFEST_REPO=git://git.linaro.org/android/platform/manifest.git
> 
> to
> 
> MANIFEST_REPO=git://android.git.linaro.org/platform/manifest.git
> 
> Old tree (git.linaro.org/android/*) was made inaccessible for the time
> being to help with updating all references to it. It should be back up
> shortly in read-only mode. (If there're immediate concerns, it's at
> git.linaro.org/android-old/ now and can be renamed back by anyone with
> git.linaro.org access).
> 
> With the spirit of making one change at time, all developers still
> should have permissions similar to what they had before: anyone can
> still create branches and push changes directly to them (*1). However,
> once we finish updating build configs and docs for new tree location,
> the next step will be setting up a workflow based on mandatory code
> review, so I'd like to invite all developers to practice that right
> away. Details on how to submit change for review are given at
> https://wiki.linaro.org/Platform/Android/Gerrit (in particular, repo
> upload works now).
> 
> (*1) The remote for such commits is different now of course, like
> this: ssh://pfal...@android.git.linaro.org:29418/platform/build .
> Replace "pfalcon" with you gerrit username and platform/build is the
> component you need.
> 
> 
> Please share any issues, concerns, and questions you may have related
> to this migration.
> 
> 



-- 
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to