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

* Update CONTRIBUTING.md to introduce Issue Tracker

Also made some template changes for issue filing

* Updating based on lararennie's suggestions

Add back number type
annoucement -> announcement
Google -> Google's

* Update CONTRIBUTING.md

Added the missing requires this detected, removed the extra require. One
missing require was added manually (goog.object) since it's unable to
detect it.

Updated the readme: compiling everything seems to work at the moment.

* [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.

Linking to FAQ from the README, and updating broken links in the two files while here.

-- 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.

It was unreadable and obsolete. A link to fresh javadoc (and can be
changed to be per version) is available in the README.

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

Adding FAQ about why we don't support countries like Bouvet Island, Yugoslavia, Antarctica etc. and what our rationale is for supporting a country.

Update typos in old release notes

Two releases in 2012 were labeled as 2010.

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

Update README.md

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

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

Add FAQ for Android resource loading

* [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