Hi,
Linaro Android has now moved up to 2.3.5.
The daily builds (https://android-build.linaro.org/index) are now based on the linaro_android_2.3.5 branch of the manifest.
Please rebase any dev_branches you have to 2.3.5. The linaro_android_2.3.4 branch will no longer be supported.
Regards Patrik
On Wed, 17 Aug 2011 11:00:32 +0200 Patrik Ryd patrik.ryd@linaro.org wrote:
Hi,
Linaro Android has now moved up to 2.3.5.
The daily builds (https://android-build.linaro.org/index) are now based on the linaro_android_2.3.5 branch of the manifest.
Please rebase any dev_branches you have to 2.3.5. The linaro_android_2.3.4 branch will no longer be supported.
And another quick reminder just in case somebody missed it before - Linaro Android tree has moved to http://android.git.linaro.org/ , so if you're still using old checkout, this is good timing to do fresh checkout for 2.3.5 upgrade.
https://wiki.linaro.org/Platform/Android/GetSource has more info, as usual.
On Wed, Aug 17, 2011 at 12:16:36PM +0300, Paul Sokolovsky wrote:
On Wed, 17 Aug 2011 11:00:32 +0200 Patrik Ryd patrik.ryd@linaro.org wrote:
Hi,
Linaro Android has now moved up to 2.3.5.
The daily builds (https://android-build.linaro.org/index) are now based on the linaro_android_2.3.5 branch of the manifest.
Please rebase any dev_branches you have to 2.3.5. The linaro_android_2.3.4 branch will no longer be supported.
And another quick reminder just in case somebody missed it before - Linaro Android tree has moved to http://android.git.linaro.org/ , so if you're still using old checkout, this is good timing to do fresh checkout for 2.3.5 upgrade.
Will the old checkout break if you try and update it? If not, maybe we should make it break so people are aware of the tree moving around.
On Wed, Aug 17, 2011 at 1:40 PM, Christian Robottom Reis kiko@linaro.orgwrote:
On Wed, Aug 17, 2011 at 12:16:36PM +0300, Paul Sokolovsky wrote:
On Wed, 17 Aug 2011 11:00:32 +0200 Patrik Ryd patrik.ryd@linaro.org wrote:
Hi,
Linaro Android has now moved up to 2.3.5.
The daily builds (https://android-build.linaro.org/index) are now based on the linaro_android_2.3.5 branch of the manifest.
Please rebase any dev_branches you have to 2.3.5. The linaro_android_2.3.4 branch will no longer be supported.
And another quick reminder just in case somebody missed it before - Linaro Android tree has moved to http://android.git.linaro.org/ , so if you're still using old checkout, this is good timing to do fresh checkout for 2.3.5 upgrade.
Will the old checkout break if you try and update it? If not, maybe we should make it break so people are aware of the tree moving around.
yeah, we did that for a couple of days ( i think a week); at the point we said we probably catched most (important) consumers and decided to bring back the old URLs, to make instructions of past releases etc to work again.
We will keep reminding in announcements for a while though.
Hello Christian,
On Wed, 17 Aug 2011 08:40:09 -0300 Christian Robottom Reis kiko@linaro.org wrote:
On Wed, Aug 17, 2011 at 12:16:36PM +0300, Paul Sokolovsky wrote:
On Wed, 17 Aug 2011 11:00:32 +0200 Patrik Ryd patrik.ryd@linaro.org wrote:
Hi,
Linaro Android has now moved up to 2.3.5.
The daily builds (https://android-build.linaro.org/index) are now based on the linaro_android_2.3.5 branch of the manifest.
Please rebase any dev_branches you have to 2.3.5. The linaro_android_2.3.4 branch will no longer be supported.
And another quick reminder just in case somebody missed it before - Linaro Android tree has moved to http://android.git.linaro.org/ , so if you're still using old checkout, this is good timing to do fresh checkout for 2.3.5 upgrade.
Will the old checkout break if you try and update it? If not, maybe we should make it break so people are aware of the tree moving around.
It's read-only, but in-place to allow to reproduce our older releases (which have manifests pointing to the old location). We "broke" it (made inaccessible) for couple of days immediately after transition to draw attention and catch not updated builds/manifests quicker, but then it was put back into place. Alexander Sack was in loop on this process.
So, it's indeed a bit of dilemma - either we suddenly break older releases for people, or risk them dealing with stale code. Well, preserving releases and doing friendly reminders for some time seems like good compromise, and if there're better ideas, let's discuss them. (Need to make a post on Linaro blog actually, just need to figure out how to do that.)
-
Alexander Sack -
Christian Robottom Reis -
Patrik Ryd -
Paul Sokolovsky