Is this reasonable? One codebase for all Squeak versions? I mean, this would imply to add code that tests if the deprecated method has been removed or not, or it would not to test for the version (if version X, call method Y, else method Z). This is bound to become very messy over time...
Wouldn't it make more sense to freeze the external packages with the release (to be developed much more cautiously) while forking a new unstable branch for the new unstabe Squeak release?
We should do that. Freeze. freeze
To be backward compatible in the sense that all new versions of packages in 3.9 need to work even on old Squeak versions seems to be not really practical...
:)
Marcus