Whenever I update the master branch Metacello I run the full test suite against Pharo3.0 through Pharo6.0 (and will add 7.0) ... so the master branch is all that is needed for whatever version of Squeak, GemStone or Pharo you are using and I use Travis-Ci for running the tests ... For GemStone we run the Metacello tests against new versions of GemStone before the release of the next version of GemStone. It would be nice if Pharo did the same thing as a matter of course: run the Metacello tests against the new release of Pharo --- if not before at least close to the new release --- so that things like the change to Pragma could be found before the release ... I t would also be nice if the needed changes for Pharo were integrated into the master branch for Metacello on GitHub ... as Denis mentions, the packages are owned by the integrator so I for one am never sure what kind of changes have been made, but as long as tests are passing .... Dale On 11/14/2016 10:15 AM, Cyril Ferlicot D. wrote:
Le 14/11/2016 à 18:12, Denis Kudriashov a écrit :
But we already has fork of Metacello in image. Many Metacello packages are from integrator. So loading latest version is not possible now. And merge will not be easy task anyway. But maybe I am wrong here. For some projects as MaterialDesignLite I need the latest version of Metacello so I load it. Before the change in pragma it was fine.
Dale try to keep Metacello running on Pharo with TravisCI I think.