On Thu, Sep 17, 2015 at 9:40 PM, Marcus Denker <[email protected]> wrote: >>> >>> Also: >>> I did a simple fix on NautilusGroupAutoBuilder package - there is >>> a ConfigurationOfNautilusGroupAutoBuilder. But is it managed internally >>> or externally now? >>> >> Even I can not tell you. >> > > 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? My workflow for reviewing a submitted fix (e.g. for issue 11111) is to open the Pharo5Inbox repository and filter on the issue number, which leaves the SLICE-Issue-11111 as the only item. Having to discover where fixes are scattered makes it harder to review fixes, and they will get less review Now if the Inbox contained ConfigurationofXyz-Issue-11111, it would be simple to identify what needs to be reviewed. This might even help the CI monkey to pick up Configurations for testing. btw, it would be cool if a package loaded by a Configuration becomes dirty, then the Configuration also becomes dirty, or is otherwise flagged somehow. cheers -ben
