Hi, Indeed, I do not think it scales for the Pharo integrators to deal with all external projects. And, it actually happens rarely that changes in Pharo break Moose. I think we should not overreact :).
It should be the responsibility of the external project to ensure it can react fast. I think this gets more people involved and overall we benefit from more energy. Cheers, Doru On Thu, Jul 3, 2014 at 4:55 PM, Marcus Denker <[email protected]> wrote: > > On 03 Jul 2014, at 16:45, Stephan Eggermont <[email protected]> wrote: > > > The fix for 13422 has broken the moose build. > > https://pharo.fogbugz.com/f/cases/13422 > > > > Checking if a pharo change breaks other builds would be appreciated. > > It is essential to check for changes in all other builds, as we don't > run all > > tests in all builds. > > Doing so “by hand” is impossible. Sorry. > > Your help setting up the build server to do so would be appreciated. > But even than, we can not wait multiple hours for every tiny change… so it > would > need to be done in a way that it is *fast*. > > (right now I do not even have time to get the infrastructure working again > that > just runs all image tests on all submitted code). > > Marcus > -- www.tudorgirba.com "Every thing has its own flow"
