[Linaro-validation] LAVA Core
yongqin.liu at linaro.org
Tue Apr 17 02:29:23 UTC 2012
First I agree with this intent.
And I am a little concern on the compatibility of installation/upgrade with
the old one.
Do we have considered the method for installation and update when we use
There maybe someone already using our lava now, If we did not consideration
this maybe cause some trouble for them.
Here are some consideration from me, but don't have solution for them now:(
It's probably that we will install and upgrade with command apt-get again,
but will that can install like lava-deployment-tool we used now?
or can we update the instance that deployed with lava-deployment-tool now
at that time?
Or do we still use the lava-deployment-tool to do the instance installation
On 15 April 2012 02:14, Zygmunt Krynicki <zygmunt.krynicki at canonical.com>wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> I'd like to announce a new project in the LAVA family.
> (README file follows)
> Seriously, lava has way to many tiny pieces. It all started when we
> renamed launch-control to lava-dashboard and created lava-server in
> the process. Now it's getting in the way.
> So here we are, lava-core is the start of the merge. Subsequent
> projects will slowly merge into the core. Then one day we may just get
> a package that is called 'lava', that ships a program called 'lava'
> that does useful stuff.
> (End of readme file)
> The project has been registered on Launchpad already. I plan on
> proposing merge requests that move parts of the non-client pieces
> there. Existing projects shall remain as backwards compatible code
> imports from lava-core.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> linaro-validation mailing list
> linaro-validation at lists.linaro.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the linaro-validation