[meego-commits] 6002 accepted: Tools:SDK/kernel
kad at kad.name
Wed Jul 28 13:50:35 UTC 2010
On Wed, Jul 28, 2010 at 16:17, Wang, Kevin A <kevin.a.wang at intel.com> wrote:
> Very glad for hearing comments from you, we are very happy to try to submit our SDK changes to Trunk-Testing, and this is in our plan also, and we even want that eventually any real device images released by integration team can be run with qemu and Xephyr solution smoothly without any changes, let me explain more about our SDK integration plan, we planned 3 stages for SDK integrations:
Side comment: there is no "integration team" in MeeGo :)
> About committing the packages to Tools:SDK from devel:tools:sdk, because we want to release the ks file (using to create MeeGo SDK emulator image) to the developers, so that everyone can try to create their own MeeGo SDK emulator image based on Tools:SDK, and we could continue our development on devel:tools:sdk, we expect we can get more feedbacks and involvements from community as early as possible. Of cause, the idea case is that we could have snapshot for Tools:SDK for each of SDK release.
That's actually one thing which I'm trying to avoid - releasing SDK
outside of the product.
Make devel:sdk as your team's area for testing changes which would
eventually go to Trunk, like all other teams are developing.
Make the needed changes available within MeeGo weekly release.
Make the .ks file part of actual release (if it somehow different from
already existing in releases:
). Point community to weekly build where your image would be released
from your prepared .ks file. But don't distribute it outside MeeGo
But, please, do not mix tools packages which are installed on
developers host OS with packages which would be part of image.
And please, put some effort to make SDK within MeeGo product, not as
> Thanks again and welcome for any further questions and comments.
br, Alexander Kanevskiy
More information about the MeeGo-commits