congrats!

please verify that the license has changed to "GPLv2 or later", as in these files,
rather than simply "GPLv2" as stated on the project page.  Since many projects are
licensed GPLv3 or AGPLv3 this is vital.

We don't have the option to list gplv2 or later in the system. I'll look into that: 

The code in question is conditionally compiled into libjingle
depending on whether you have a separate library named GIPS or not.
The code is only intended as a default fallback for when GIPS does not
exist.   In addition, the code is not actually necessary for libjingle to work,
it only exists to support talk/examples/call.  The fact that it is
compiled in by default (and not just as part of the example) is
actually a bug, according to the developer.

That said, we are happy to place this version of libjingle under the
GPLv2 license.  In the future, we will simply remove the code for the
example (and the GPL code it relies on that sits in a non-example dir
right now), and release those versions under BSD again.

As an fyi... the way we denote licenses on code.google.com doesn't have a 'or any
later' clause in the drop down. We count on the users of the software to read the
licenses and abide by them. And since not -all- gplv2 apps have the or any later,
we're unlikely to add that to the default display of licenses, so that's a won't fix. 

You could shorten it to GPL2+ and offer it as an additional license.  The primary use
of the license field, in my mind, is for license compatibility - whether something is
"or later" or not is the primary factor in (L)GPLv2->(L/A)GPLv3 compatibility.