Updated project website for HttpClient 5.0-alpha1 release
git-svn-id: https://svn.apache.org/repos/asf/httpcomponents/project-website/trunk@1727148 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/site/apt/news.apt b/src/site/apt/news.apt
index 7d815c9..a290b39 100644
--- a/src/site/apt/news.apt
+++ b/src/site/apt/news.apt
@@ -30,7 +30,27 @@
HttpComponents Project News
-* 3 January 2016 - HttpComponents HttpCore 5.0-alpa1 released
+* 28 January 2016 - HttpComponents HttpClient 5.0-alpha1 released
+
+ This is a major release that renders HttpClient API incompatible with the stable 4.x branch
+ and upgrades HTTP/1.1 protocol conformance to the requirements and recommendations of
+ the latest protocol specification. This release lays the foundation for transition to HTTP/2
+ as the primary transport protocol in the future releases.
+
+ Notable changes and features included in the 5.0 series are:
+
+ * Improved conformance to requirements and recommendations of the latest HTTP/1.1 protocol
+ specification (RFC 7230, RFC 7231, RFC 7235)
+
+ * Package name space changed to 'org.apache.hc.client5'
+
+ * Maven group id changed to 'org.apache.httpcomponents.client5'
+
+ * By default the maximum connections per route limit is set to 5
+
+ * By default connection request timeout and connect timeout are set to 3 minutes.
+
+* 3 January 2016 - HttpComponents HttpCore 5.0-alpha1 released
This is a major release that renders HttpCore API incompatible with the stable 4.x branch
and upgrades HTTP/1.1 protocol conformance to the requirements and recommendations of the
diff --git a/src/site/apt/status.apt b/src/site/apt/status.apt
index dbb36b7..b24f342 100644
--- a/src/site/apt/status.apt
+++ b/src/site/apt/status.apt
@@ -48,6 +48,12 @@
maintained and supported. Users of all versions of HttpClient are advised to upgrade to the
latest release of the 4.5 series.
+* {HttpComponents HttpClient 5.x}
+
+ HttpClient 5.x branch is the current unstable development branch. The main focus of the 5.0
+ series is ensuring full compliance with RFC 7230, 7231, laying a foundation for transition to
+ HTTP/2.0 and incremental API improvements.
+
* {HttpComponents HttpAsyncClient 4.1.x}
HttpAsyncClient 4.1.x branch is considered stable and production ready. It is being actively