Marcus Denker wrote: 
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?

    


The rational is: Simplify API evolution.

If we deprecate a method in Pharo4, people like to change their code base *and* use the
same code on Pharo3.
(Zinc is one example of that).

So for simple �rename� changes like this, we can reduce the pain of people *a lot* by providing the
same method in Pharo3. Keep in mind that we do *not* do the actual change of rewriting all senders
and deprecating the old method. That is just done in Pharo4.

	Marcus
This policy will help a lot.� Now I wonder if these should all be added into a package named something like "Pharo4-forward-compatibility" - to make it obvious when the backported method appears as extensions - to reduce Pharo 3 looking like a moving target --- as long as its not much additional effort.
cheers -ben