> ----- Original message ----- > From: "Carsten Munk" <[email protected]> > To: "Clark, Joel" <[email protected]> > cc: "[email protected]" <[email protected]> > Subject: Re: [MeeGo-dev] Urgent: We need community ftp space or similar > Date: Wed, 1 Dec 2010 19:53:10 +0100 > > For good measure - thanks for explaining these issues - we're not > disagreeing that it would be a good thing to be part of the release > process :) > > I think the problem was/is the procedures for getting to be part of > release process isn't well-explained or even specced out on wiki > anywhere (tacit knowledge in us that works in Release Engineering). > > You've helped get a better look at this and how to get BeagleBoard > images into release process - and thanks for that. > > Maybe we should work this thread into explaining how to become part of > release process in practice? I think there's many teams around who's > not sure where they should put on-going MeeGo work and be a part of > the release process. >�
Good points Carsten, as�this naturally goes beyond Beagleboard, as TI is demonstrating with Pandaboard:� http://www.slideshare.net/menonnishanth/meego�,�http://pandaboard.org/content/meego-arm-unofficial-hardware-adaptation � -Randy -------------------------------------------------------------- Ovi Mail: Making email access easy http://mail.ovi.com
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
