Hello John, I'd like to follow up on IRC conversation we had during "Android Common Tree & Upstreaming" at LDS https://blueprints.launchpad.net/linux-linaro/+spec/linaro-kernel-o-android
May 11 10:49:08 <pfalcon> jstultz_vm: what about "continuous merging" of linaro tree with android patches (that's exactly why I asked about maintaining a separate patch ;-) ) May 11 10:49:46 <jstultz_vm> pfalcon: so i can do that, but part of it is the time required to validate that the combination didn't break anything. May 11 10:49:52 <jstultz_vm> (which has happened in the past) May 11 10:50:06 <jstultz_vm> that load causes me to not update constantly.. May 11 10:50:58 <jstultz_vm> i could just update it every week/few days. but i'm hesitant to push out a tree that breaks folks. I agree that no immediate changes to the process should be done, we should get 11.05 release out, hopefully with fixes for known regressions or missing features. I'm just trying to wrap my mind on how we'll bootstrap Continuous Integration in the next cycle, which is not far away. So, I just would like to make sure that all teams involved are on the same line to make CI work effectively, i.e. that kernel team is able to update Android kernel regularly, infrastructure team has build system which produces Android images reliably, and validation team has all hooks needed to start testing them as soon as they are built. So, I guess validation team would lead on CI start-up sequence, when they have all needed infrastructure and testsuites integrated. In particular, I'm waiting from them for details on how build notifications should be communicated to the LAVA system. -- Best Regards, Paul _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
