On Fri, May 11, 2012 at 3:43 AM, Andy Green <andy.gr...@linaro.org> wrote: > On 11/05/12 08:27, Somebody in the thread at some point said: > >> 4. in between RCs, we only move mainline on our linux-linaro release >> baseline forward if we see a working tracking build that wouldn't drop >> any topics that already made it into this RC cycle. > > > The probability of getting a good unified tree follows the kernel cycle, we > all have good reasons to have tried to arrive at a good, working, release. > Sometimes we only get a reasonably good result a week or two after Linus' > release. > > For that reason maybe you should just be trying to 'release' a release-basis > unified tree, ie, the 3.4 one targeted now as the deliverable. It still has > meaning to make a monthly release of that since it can collect stable > mainline updates and updates from each LT release tree that happened in the > meanwhile. > > We do need to create these intermediate unified trees so we know what to fix > on our trees so they can go in smoothly, but it matters less then if one day > half the LT trees are missing on it since it's of interest only for LTs and > platform guys to study what else needs solving on the LT trees. > > I still think you won't get anywhere useful until we are trying to build the > unified trees for real. Then we can start the needed work to make them fit > together properly, until then we're treading water in "technical debt". > Discussing how to run the tree is something to do later after gaining this > experience. > > I had a look at the LT gits > > ARM Merge-managed integration-linux-vexpress 3.4-rc4 > TI Rebase-managed tilt-tracking 3.4-rc4 > Freescale Merge-managed lt-3.4 3.4-rc3 > Samsung Rebase-managed tracking 3.4-rc3 > STE Merge-managed integration-linux-ux500 3.4-rc6 > > (wow STE - on igloocommunity.org - have a LOT of patches! I thought we were > leading the way) > > Actually locally TILT are on -rc6 but there was almost no conflict coming > between -rc4 and -rc6. If you take the approach to merge these trees, I > found that late in the cycle it's usually pretty forgiving about some > variation in basis. > > So why not give these all a test merge today and see what starts falling > out? I am sure we all have something to fix and there may be larger issues
I will check with Andrey/Ricardo if we can do that :) ... would it be exciting enough if we just try adding TI to the mix this month (and not all?)? In any case, you should definitely send Andrey a list of topic branches you want to register for linux-linaro and things will get picked up as soon as Andrey can I guess :). -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs 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
