Christophe Demarey wrote
As a general purpose reflexion on dependencies conventions, I would say: If you are in development mode, it makes sense to rely on latest versions of dependencies (bleeding edge) to be able to detect integration problems as soon as possible. If you are in a release mode, you should ensure that your code can run at least on fixed dependencies versions
+1 to the two different modes. Dale had recommended to me to depend on #stable in the baseline and then a specific version in the version. I'd say it depends on the underlying project - something like Zinc which seems to always be rock-solid at the bleeding edge I'd probably put #bleedingEdge in the baseline, where a less stable project I might use #stable. But I say definitely, definitely, definitely use a stable version in the version (unless it's a really loose dependency like OB for Seaside) - people need to be able to depend on loading a specific version being repeatedly identical. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-configuration-conventions-tp4681777p4682035.... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.