Sept. 18, 2014
12:34 p.m.
On 18 Sep 2014, at 14:30, Sean P. DeNigris <sean@clipperadams.com> wrote:
GitHub wrote
14018 backport #uncapitalized to Pharo3
Not a big deal, but this doesn't seem to fit our bugfix-only backport policy. What was the rationale?
To allow external framework writers to target both 3 and 4 when renames/deprecations occur. Without moving the new method to 3, there is a catch 22: - either use the old API -> deprecation warning on 4 - either use the new API -> not available on 3 This will of course not be done for every change ;-) Marcus explained this in more detail in a mail.