Obviously the devil's in the details of the terms of the CLA. I had previously thought the purpose of the CLA was to allow the projects organizers to make copyright claims in court, not to allow them to re-license.
http://www.cnet.com/news/linux-to-gplv3-a-practical-matter-n...
As long as contributors are licensing their contributions under the terms of the GPLv2, they're also licensing them under all future versions.
No it doesn't. The relevant part of the license is:
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
ie, it's optional to use the "or any later version" language.
You only need them to license their code under "GPLv2 or later" while you license the project only under "GPLv2". This way you're free to upgrade the license if and when you want.
On the other hand, without signing over your rights, you can effectively hold up a project from moving forward. For example, if a project wanted to move from GPLv2 to GPLv3, IIRC, you can't do that without the permission of all contributors unless they have signed over their rights. And as @trestletech has pointed out not all contributors are created equal[1].
One the one hand, you have people making significant contributions (and you don't want to just stomp all over them), on the other hand you could have people making tiny contributions, yet are holding up everyone else.
[1]: https://github.com/datastax/nodejs-driver/commit/6f3c6b2f454...