The pivot of controversy is the following paragraph of the policy:
After a new major version of Spring is released, community maintenance updates will be issued for three months to address initial stability issues. Subsequent maintenance releases will be available to SpringSource Enterprise customers. Bug fixes will be folded into the open source development trunk and will be made available in the next major community release of the software.The move will almost definitely cause profound repercussions in the Spring ecosystem. I primarily expect two major effects: the rise of in-house Spring distributions based on the development trunk in larger IT shops and springing into existence (a pun intended) of independent community-based distributions of Spring framework a la CentOS vs RedHat Linux.