2010/12/1 Clark, Joel <[email protected]>: >> I don't understand why all of this is necessary before you can allow >> someone to upload an image & publish a URL to it, so that interested >> parties can download & play with it. Creating the necessary bugzilla & >> build stuff will add hours or days to requests, and is not a scalable >> approach to community builds. > >> Cheers, >> Dave > > It's not that hard. Just need a maintainer volunteer can work within the > MeeGo build system to make images for everyone to work with rather than > keeping > this stuff private and unmaintained. > > OK fine. I've tried more than I probably should. If anybody decides they want > to see Beagleboard images built within the MeeGo build system and are willing > to > work to make that happen please speak up. Until then I'll shut-up.
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. BR Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
