linaro-release team mailing list archive

[Ryan Harkin <ryan.harkin@xxxxxxxxxx>]

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.


>
> 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.

Now that we've got a proven build from linux-linaro, I'm happy to drop the
LT builds and have only the linux-linaro ones.  Then, any failures that we
wouldn't have expected would be defects/regressions (when compared to what
happens if using the LT tree).

I don't speak for the other LTs of course, all of whom have a more complex
situation than my team.


> Cheers,
> --
> Ricardo Salveti de Araujo
>