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 lava-core?
There maybe someone already using our lava now, If we did not consideration before,
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 and update?
Thanks,
Yongqin Liu.
On 15 April 2012 02:14, Zygmunt Krynicki
<zygmunt.krynicki@canonical.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
I'd like to announce a new project in the LAVA family.
(README file follows)
http://xkcd.com/927/
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.
Thanks
ZK
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPib6QAAoJEOvx/vtfL8ZXXgQP+QHhT/4beTTW7+yCFehDwe6i
iDNZVPAhjrXxeh8TFisfdnPP+8z9khkcQTyXOgJnC3T4vbmWNBTjDQTpkSg/0lzS
O8a0YBkcdQ5RPDr1NNiLG7PoAJDUts8yY2DXk2C1ykWmqOZBw7NcRVaX/gQ1Ym75
JODbrtcO1vT+E5rBNYiEgMEELStJZfMGbfGzFI+d4ONz702SJNVDHcY7FReKuTDc
nvOZ8zfW03fHFNobAAR5F57lGBz6oLZjz/nblsCJjA9tf20LPsQTUxkv6EkkEyd1
0CTkjQt60kHQB/FYoxLofJ76CR12gGGNLauAf+fQPBa4CG5MvMsd7fdDbMVa3iZh
MKzOv206SPTmB7GHRVTfTqoeFwsXNEc7CnFvEWA9GbCUboqBxuYnEw95m1137+/7
B3XHqsBmuJC1KJrwNIAFTl41oRuHchwEeZv72wBxoMU+4MKVpHFz6F0P3aR9da4s
Uty9z+Nk8lUyQBGMOy6GMzqlPnNNYPM/v3f0CBZkA+D9mtdD/pFJGkhm/xmyE23S
5NskNi7CXZ+m+kyONAzL3JagLnB7PE+L8tHbap3IKbxkPbB5kzz/3eWqK6Evq+3t
eQJZzuEq8gmIzyHVYjtnRvWXigv3m/vQrkcFC9Gs36tNXG0lEO07DbLpj3ZTlQ03
K+VSjvjsNhMvdhitIY7I
=DKzA
-----END PGP SIGNATURE-----
_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation