Metadata updates for release 7.0.5

[platform/upstream/libphonenumber.git] / java / release_notes.txt

diff --git a/java/release_notes.txt b/java/release_notes.txt
index 1db5019..715ca1c 100644 (file)
--- a/java/release_notes.txt
+++ b/java/release_notes.txt
@@ -1,3 +1,32 @@
+Apr 23, 2015: libphonenumber-7.0.5
+* Metadata changes:
+ - Updated phone metadata for region code(s):
+   AF, AS, BD, BE, CA, CI, IN, JM, KH, LI, LU, MU, NE, PL
+ - Updated short number metadata for region code(s): BE, LI
+ - Updated geocoding data for country calling code(s):
+   86 (en, zh), 358 (en, fi, se)
+ - Updated carrier data for country calling code(s):
+   32 (en), 93 (en), 225 (en), 227 (en), 855 (en), 1684 (en), 1876 (en)
+
+Mar 25, 2015: libphonenumber-7.0.4
+* Metadata changes:
+ - Updated phone metadata for region code(s): CA, HU, IL, JO, LU, SG, SL, US
+ - Updated short number metadata for region code(s): BI
+ - New geocoding data for country calling code(s):
+   1220 (en), 1628 (en), 1629 (en)
+ - Updated carrier data for country calling code(s):
+   65 (en), 232 (en), 972 (en)
+
+Mar 02, 2015: libphonenumber-7.0.3
+* Metadata changes:
+ - Updated phone metadata for region code(s):
+   AR, BH, BY, CI, CN, GH, KR, KW, LU, ME, NZ, SB, WS
+ - New geocoding data for country calling code(s): 64 (en)
+ - Updated geocoding data for country calling code(s):
+   86 (en, zh), 1418 (en), 1438 (en), 1450 (en), 1514 (en), 1819 (en)
+ - Updated carrier data for country calling code(s):
+   225 (en), 233 (en), 677 (en), 973 (en)
+
 Jan 09, 2015: libphonenumber-7.0.2
 * Metadata changes:
  - Updated phone metadata for region code(s):
@@ -430,7 +459,7 @@ Oct 10, 2012: libphonenumber-5.2
  - Adds isNumberGeographical() method.
  - Adds getRegionCodesForCountryCode() method.
  - Fixing issue with getSupportedGlobalNetworkCallingCodes()
-   [http://code.google.com/p/libphonenumber/issues/detail?id=202]
+   [https://github.com/googlei18n/libphonenumber/issues/202]
  - Ensures that returned collections are unmodifiable where necessary
    [there is a very slight risk that this may break existing users who were relying on being able
    to modify these collections, but doing so would be breaking lots of other assumptions that this