no, fixes in 3.0 goes in Pharo30Inbox. the one that is bad is the validator⦠but AFAIK, it even shouldnât be running :P I will take a look tomorrow at your changes. Esteban On 13 Aug 2014, at 19:08, Ben Coman <btc@openinworld.com> wrote:
Where should we be putting slices for Pharo 3 backports. I am proposing my fix for "Extended Search... Implementors fooled by block variables" be backport for Pharo 3. I took a guess that Pharo30Inbox would be the place to put the slice, but the the report [1] from the monkey reports:
Jenkins Job jenkins-Pharo-3.0-Issue-Validator-27054 Could not Find Change: http://smalltalkhub.com/mc/Pharo/Pharo40Inbox/main
So should Pharo 3 backports be put in Pharo40Inbox? (probably easiest short term workaround?) Or does something with the monkey need to be changed? (maybe longer term goal?)
cheers -ben
[1] https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/27054//artifact/vali...