Document how changes in Google's base library are included or not about libphonenumber-csharp HOT 2 CLOSED

I can look into putting some updates and improvements to the readme in the next week or so. The metadata isn't updated fully automatically (however fairly close to it) and I usually have it updated in a day or two. The library version matches the Google metadata version.
Actual functional code changes do not currently have a policy for when or if they are ported; bugfixes or other small tweaks are usually done immediately, new features are ported on an ad hoc basis at this point (contributions certainly welcome).

I'm not able to view that Issuetracker link however, if you perhaps have suggestions on better phrasing, I'm intending to mean if you see a behavior that you think is wrong, to then test the number withe the linked demo. If this library and the google demo agree than an issue should be filed with them, if they disagree file an issue here. Happy for suggestions for better ways to explain that, you can find plenty of past issues where I have to point people over.

from libphonenumber-csharp.

Thank you for looking into it. Just a small note like the comment above would be sufficient for me getting to understand the maintenance process without bothering maintainers.

The Issuetracker link is just some bug report on the Dutch number representation, which might or might not make it into an improvement for libphonenumber. The Google original version has that issue too, so that's why it was reported primarily there since that might benefit the most people.

from libphonenumber-csharp.