version update

CHANGELOG.md

@@ -1,4 +1,6 @@
-## [v3.20-2016d] not yet released
+## [v3.21-2016e] not yet released
+
+## [v3.20-2016d] published on 2016-05-07
 ### Added
 - Related gregorian year for non-gregorian calendars [#370]
 - Modern-coverage of languages defined in CLDR [#367]
@@ -8,6 +10,7 @@
 - Support for Esperanto [#495]
 
 ### Fixed
+- Make alias zone identifiers always parseable [#500]
 - Improve performance of parsing timezone names [#499]
 - Clarify format behaviour if zoneless types are combined with zone names [#490]
 

README.md

@@ -21,7 +21,7 @@ from the Android platform they fail to hold their own i18n-resources. But real-w
 Android platform often use very different text resources and data for world languages, dependent on how up-to-date
 the Android OS-version is. Furthermore, even the newest Android platform does not offer the best available 
 quality of i18n-translations (an example is missing support for localized plural rules in formatting of durations).
-Time4A closes this big gap **supporting actually 72 languages** and has more features than any other date and time
+Time4A closes this big gap **supporting actually 80 languages** and has more features than any other date and time
 library available for the Android platform. Of course, Time4A also supports the **newest timezone data** available
 at [IANA](http://www.iana.org/time-zones). On the other side: If you really want you can even use the platform timezone
 data in parallel. Time4A gives you the freedom which timezone data to use.
@@ -33,7 +33,7 @@ Only two steps are required before coding against the API of Time4A.
 
 ```groovy
 dependencies {
-    compile group: 'net.time4j', name: 'time4j-android', version: '3.19-2016d'
+    compile group: 'net.time4j', name: 'time4j-android', version: '3.20-2016d'
 }
 ```