Carsten Munk wrote: >> Joel Clark wrote: >> I don't get it either. If the "long-time, active community member" >> is willing to build, test, upload, >> distribute and deal with problems >> from anybody who uses his image, why not take advantage of the existing >> automated processes for code management, build, distribution and issue >> tracking? Is the goal here to make >>sure the beagleboard is not supported >> on meego.com? > > I think we're going in a circle here. > > Long story short: > > When development is being done, especially proof of concepts, there > will always be images created that doesn't fit in an ordinary release > process. But has to be shared with a MeeGo contributor audience such > as a team. So what's proposed is an exchange area, where people can > upload and other people download. Images would be deleted after a time > period.
That's why I pointed to the build repos, not the release repos. You describe exactly what they are for. > It would also make sure that teams don't end up using internal > company infrastructure for such things - like we do with our > acceptance/sanity images currently. I'm not sure what "internal company infrastructure" you are referring too. I was referring to the LF MeeGo.com infrastructure. > An example can be for example development images related to > integrating a new graphics driver where I'd have to share it with QA > guys to verify nothing is going sour. i.e. build repos > For the Beagleboard image, such an area would allow for a process > where the kickstart file is evolved to an initial working state, > images published to the relevant teams and interested contributors. > Based on that work FEA#'s set up for the hardware adaptation, the > needed roles attached and included as part of the real release > process. That's obviously where things should go eventually. But in > the very early stages, release process is overkill for the initial > images to get things started. i.e. build repos > .. I don't think we should be in a position where we put any incoming > hardware adaptation, even the proof of concepts into the MeeGo release > process. If something is released from repo.meego.com it should be > quality. Agree about the use of release repos > BR > Carsten Munk regards Joel _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
