* Handling possible out-of-bounds exception that would be thrown in C++
and Java if a number with a phone-context tag is entered (RFC3966
format) but no actual phone context.

* [maven-release-plugin] prepare release v8.4.1

* [maven-release-plugin] prepare for next development iteration

* Metadata updates for release 8.4.1

* Update release_notes.txt

IS_POSSIBLE_LOCAL_ONLY and INVALID_LENGTH are now being returned from IsPossibleNumberWithReason.

The enums were added in v8.3.0

Groups announcement: https://groups.google.com/forum/#!topic/libphonenumber-discuss/sPhYzdzFCmg

* Updating docs for getRegionCodeForNumber to clarify that it does not work for short codes or invalid numbers.

* [maven-release-plugin] prepare release v8.4.0

* [maven-release-plugin] prepare for next development iteration

This adds a JAR target without included metadata. Third parties using this
variant may supply their own metadata via a custom MetadataLoader.

-- Changing response writer to make it UTF-8. Now carrier/geocoding results have unicode support and don't output "?" characters.
-- Fixing pom file to remove the "repositories" block, now the demo builds on maven. Reordered some other fields to match other pom files. Added some other minor attributes.

Update doc references to refer to CLDR and the page of CLDR codes where
appropriate - it used to say ISO country codes were used, but they aren't.

Also updated to refer to two *or three* letter language codes since they may be three letters (we use the shortest defined one for a language)

Updating comments about leadingDigits field at territory level as well.

* [maven-release-plugin] prepare release v8.3.3

* [maven-release-plugin] prepare for next development iteration

- make them more consistent with each other
- explain why the empty string is sometimes returned when geocoding

* [maven-release-plugin] prepare release v8.3.2

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.3.1

* [maven-release-plugin] prepare for next development iteration

Fix for getNationalSignificantNumber to be robust in the face of malicious input (negative number of leading zeros in the phone number proto).

* [maven-release-plugin] prepare release v8.3.0

* [maven-release-plugin] prepare for next development iteration

* isNumberMatch fix for numbers with italian leading zero fields set. Only
affects people who haven't correctly constructed phone numbers using
methods like 'parse'.
* Adding C++ tests and fixing bug in ExactlySameAs method, which wasn't
updated to handle the number_of_leading_zeros field when that was added
to the phone number proto.

See pending_code_changes.txt for more details.

- Adding new enums IS_POSSIBLE_LOCAL_ONLY and INVALID_LENGTH for
ValidationResult, to be later returned by IsPossibleWithReason.
- Documenting existing enum values better.

See email on discuss list:
https://groups.google.com/d/msg/libphonenumber-discuss/sPhYzdzFCmg/6tYsS1f6DgAJ

* [maven-release-plugin] prepare release v8.2.0

* [maven-release-plugin] prepare for next development iteration

* Metadata updates for release 8.2.0

* Update release_notes.txt

* Make normalizeDiallableCharsOnly public and port it to javascript,
making use of it in the code in parallel places to the Java
implementation.

* [maven-release-plugin] prepare release v8.1.0

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.0.1

* [maven-release-plugin] prepare for next development iteration

* Support semicolon as extension character while parsing

* Add notes to pending_code_changes.txt

* JS port: Support semicolon as extension character while parsing

* Update comments in phonenumberutil.js

This excludes editing the proto file itself, or the auto-generated or hand-crafted fields that are derived from it.

* [maven-release-plugin] prepare release v7.7.4

* [maven-release-plugin] prepare for next development iteration