> On 19 Sep 2015, at 10:39, Marcus Denker <[email protected]> wrote: > > >>> >>> I think the rule we should adopt: if there is a dedicated repository >>> defined in the image for a package, people should commit >>> there. If there is non (just the inbox), then this should be used (with the >>> Slice mechanism). >>> >>> The repositories in the image should be already up to date, I think. >>> >>> Marcus >>> >>> >> >> How would the CI monkey work with Configurations from other repositories? >> > I does the check the same as for slices. (Which is great).
but the configuration needs to be copied into the inbox, of course :) > > What is a bit harder is reviewing the changes. But as the idea of external > packages is that > there is a maintainer, I actually just trust them: A configuration where the > tests go trough > I integrate without looking at it, as that is the job of the maintainer that > created the Config. exactly. the idea is to have maintainers for configurations, then relieving a bit the work of the integrator. that’s what happens with GTools, Zinc, etc. Anyway… I want to do a “configuration diff” to be able to check what a new configuration will bring… is not so hard, but you know… time time time :) what we are still struggling is with the best way to inform those changes. Because having a commit report that says “Update GTools”, does not says a lot about the bugs fixed upstream :) Esteban > > Marcus
