Didn’t we switch to the strategy integrate first into Pharo and notify maintainer afterwards? It is hard to follow because sometimes integration goes directly into Pharo with slices and other time, it is included through configurations.
I will produce a new version of the config and update the issue. > Le 16 sept. 2016 à 13:25, [email protected] a écrit : > > Whoever maintains DependencyAnalyser: There is a fix ready since 22 August > 2016. > > We need to get this into the system *soon*. > > > https://pharo.fogbugz.com/f/cases/18963/DANode-browseClass-sends-unimplemented-fullOnClas > > > Marcus
