linaro-release team mailing list archive
-
linaro-release team
-
Mailing list archive
-
Message #01662
Re: Ubuntu LEB 12.04 RC Builds
On Wed, Apr 25, 2012 at 11:48 AM, Ryan Harkin <ryan.harkin@xxxxxxxxxx> wrote:
>
>
> On 25 April 2012 15:26, Ricardo Salveti <ricardo.salveti@xxxxxxxxxx> wrote:
>>
>> On Wed, Apr 25, 2012 at 10:51 AM, Ryan Harkin <ryan.harkin@xxxxxxxxxx>
>> wrote:
>> > On 25 April 2012 14:18, Ricardo Salveti <ricardo.salveti@xxxxxxxxxx>
>> > wrote:
>> >>
>> >> On Wed, Apr 25, 2012 at 9:59 AM, Paul Larson <paul.larson@xxxxxxxxxx>
>> >> wrote:
>> >> > On Wed, Apr 25, 2012 at 7:53 AM, Ricardo Salveti
>> >> > <ricardo.salveti@xxxxxxxxxx> wrote:
>> >> >>
>> >> >> On Wed, Apr 25, 2012 at 3:53 AM, Jon Medhurst (Tixy)
>> >> >> <tixy@xxxxxxxxxx>
>> >> >> wrote:
>> >> >> > On Tue, 2012-04-24 at 19:00 -0300, Ricardo Salveti wrote:
>> >> >> >> - Vexpress (linux-linaro):
>> >> >> >> http://snapshots.linaro.org/precise/hwpacks/vexpress/1/
>> >> >> >> - Vexpress LEB:
>> >> >> >> http://snapshots.linaro.org/precise/hwpacks/lt-vexpress/1/
>> >> >> >> - Here it'd be ideal to test both, and if they have the same
>> >> >> >> list
>> >> >> >> of
>> >> >> >> functionalities and bugs, we can start using the linux-linaro one
>> >> >> >> as
>> >> >> >> the LEB
>> >> >> >
>> >> >> > What's the difference between these two? Is 'lt-vexpress' just the
>> >> >> > ARM
>> >> >> > LT topic branches, and 'vexpress' the linux-linaro branch, i.e.
>> >> >> > includes
>> >> >> > other LT and WG topics?
>> >> >>
>> >> >> lt-vexpress is produced from the LT kernel tree, and the 'vexpress'
>> >> >> only produced from linux-linaro. I got both because before switching
>> >> >> officially to the one from linux-linaro, we need to make sure it's
>> >> >> delivering at least the same functionalities.
>> >> >
>> >> > So do both need to be fully tested for release purposes? Or is there
>> >> > some
>> >> > subset of tests that can be run to make this determination?
>> >>
>> >> Hard to say, because I believe only covering all the tests would be
>> >> enough for us to find if the linux-linaro tree is at least in the same
>> >> shape as the LT one.
>> >
>> >
>> > I tested them both, just to be safe. And they both work the same.
>>
>> Great, thanks for testing them.
>>
>> >> We can simply just test the linux-linaro based one, as done by
>> >> Android, but then we'll be switching the kernel at the LEB without
>> >> having any data to compare if the results are at least expected.
>> >>
>> >> Guess we need to discuss better how we'll be doing the linux-linaro
>> >> LEB transition, as this will probably happen with the other flavors
>> >> soon.
>> >
>> > In my opinion, as far as the linux-linaro tree gives the same
>> > functionality
>> > as the LT tree, then we can stick with the linux-linaro tree. As we
>> > have
>> > parity at the moment, I'm all for having only one build. Keeping both
>> > lt-vexpress and vexpress will only confuse our users.
>>
>> Do you know if it would be useful for your team to have the
>> lt-vexpress hwpack during the dev cycle? This hwpack can be used to
>> validate the work done at the lt tree before having the
>> topics/branches at linux-linaro.
>
>
> That's a good point. What I'm trying to avoid is having two hwpacks in the
> releases, one LT and one linux-linaro, like we had a couple of months ago
> with platform's vexpress hwpack the the LT's own hwpack.
>
> But you're right, having a pure LT hwpack during the cycle for us to do our
> own testing is a useful tool.
>
> So, lets keep the snapshot builds of the hwpacks, but only push the
> linux-linaro out for releases. Of course, if linux-linaro is broken come
> release time, I may be asking if we can push the LT hwpack for that cycle
> ;-)
Sounds fine, that's exactly what we had in the past when selecting
which one would be used as the 'LEB' one. Let's just use the one from
linux-linaro this time then (for vexpress).
Thanks,
--
Ricardo Salveti de Araujo
References