On 23 Sep 2014, at 17:14, Ben Coman <b...@openinworld.com> wrote: > Esteban Lorenzano wrote: >> Hi, >> >> This is a message for people doing fixes in Pharo core, and because of that >> doing SLICEs. Since last week I’m changing the integration process >> (something transparent for most of you), to make it more automated… > > I guess the observable result is this comment on Issue 14049... > "Resolved (Fix Integrated) and assigned to Ben Coman by Ulysse The Galactic > Monkey From Outer Space > In 40240" > > Very cool. What is the trigger? Does it just pick up those issues with > status "Resolved (Fix Reviewed by the Monkey)" or is there some interface > that a group of integrators use to queue issues for integration?
well… we could automate from “fix to include” to trigger an integration. But we still want a last level of control (to human verify the change)… so for now that last step (the “accept” trigger) is made by a small app I just finished. Not that this cannot change in the future, of course… but I would like a voting system, to complete automate the integration, not just because an issue is validated that the monkey, it has to be in the image. Of course I’m talking about additions, not just bugfixes… anyway right now is almost there… :) Esteban > > cheers, Ben > >> so I added two new fields to the issue tracker: >> - preload >> - postload >> >> So… from now, if your SLICE requires one or/and the other, you need to fill >> those fields… it will not be part of the comment fields anymore. >> thanks, Esteban >> >> > > >
