Hello Under the radar, we are actively continiously cleaning Pharo deep core so that we can work on new features. For metacello, in Pharo 13 we introduced a strict mode (so that we can detect hidden dependencies), and other loading features to support module experimentations. It will make Pharo code more robust in the long term. Since a couple of months we are actively simplifying/cleaning Metacello (as the version available in Pharo) because we want to introduce new features such as the possibility to force the reload of baselines and others. Now the unit test coverage of metacello is quite low and we do not use/know all the features that are available and that you may rely on. So we would love to have beta testers that can just try to load their code in Pharo 14 alpha and report potential bugs or features drop we would have introduced. So do not hesitate and this is a nice way to help pharo S.

Nice, Metacello needs some love. I will try with our repos and report back if any problems arise. Are there any docs or details on the strict mode? Is it enabled by default, or do we need to enable it per repo? I can give it a try too. Regards, Gabriel On Mon, Dec 29, 2025 at 5:55 AM stephane ducasse <stephane.ducasse@inria.fr> wrote: > Hello > > Under the radar, we are actively continiously cleaning Pharo deep core so > that we can work > on new features. > > For metacello, in Pharo 13 we introduced a strict mode (so that we can > detect hidden dependencies), > and other loading features to support module experimentations. It will > make Pharo code more robust > in the long term. > > Since a couple of months we are actively simplifying/cleaning Metacello > (as the version available in Pharo) because we want to introduce new > features such as the possibility to force the reload of baselines and > others. > > Now the unit test coverage of metacello is quite low and we do not > use/know all the features > that are available and that you may rely on. > > So we would love to have beta testers that can just try to load their code > in Pharo 14 alpha > and report potential bugs or features drop we would have introduced. > > So do not hesitate and this is a nice way to help pharo > > S.

Hi Gabriel Happy new year > Nice, Metacello needs some love. Indeed :) And we are making progress. > I will try with our repos and report back if any problems arise. Excellent. > > Are there any docs or details on the strict mode? Not that I remember. Guille can tell us. > Is it enabled by default, No because nothing would work :) > or do we need to enable it per repo? I can give it a try too. I will ask Guille to tell us. > > Regards, > Gabriel > > On Mon, Dec 29, 2025 at 5:55 AM stephane ducasse <stephane.ducasse@inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: >> Hello >> >> Under the radar, we are actively continiously cleaning Pharo deep core so that we can work >> on new features. >> >> For metacello, in Pharo 13 we introduced a strict mode (so that we can detect hidden dependencies), >> and other loading features to support module experimentations. It will make Pharo code more robust >> in the long term. >> >> Since a couple of months we are actively simplifying/cleaning Metacello (as the version available in Pharo) because we want to introduce new features such as the possibility to force the reload of baselines and others. >> >> Now the unit test coverage of metacello is quite low and we do not use/know all the features >> that are available and that you may rely on. >> >> So we would love to have beta testers that can just try to load their code in Pharo 14 alpha >> and report potential bugs or features drop we would have introduced. >> >> So do not hesitate and this is a nice way to help pharo >> >> S.