Add 5.0

doc/sphinx/whats-new/changes.rst → doc/sphinx/whats-new/changes-4.1.rst

-.. _whatsnew_changes:
+.. _whatsnew_changes_4_1:
 
 Changes in Varnish 4.1
 ======================
@@ -8,7 +8,7 @@ in Varnish 4.0.
 
 
 Proactive security features
-===========================
+---------------------------
 
 New in 4.1 is support for different kinds of privilege separation methods,
 collectively described as jails.
@@ -24,7 +24,7 @@ now must be run in a context with `varnish` group membership.
 
 
 Warm and cold VCL configurations
-================================
+--------------------------------
 
 Traditionally Varnish have had the concept of active and inactive
 loaded VCLs.  Any loaded VCL lead to state being kept, and a separate
@@ -69,7 +69,7 @@ release unnecessary state when a VCL is transitioned to cold (see
 
 
 PROXY protocol support
-======================
+----------------------
 
 Socket support for PROXY protocol connections has been added. PROXY
 defines a short preamble on the TCP connection where (usually) a SSL/TLS
@@ -96,7 +96,7 @@ in ``vcl_recv`` to see if traffic came in over the HTTP listening socket
 
 
 VMOD backends
-=============
+-------------
 
 Before Varnish 4.1, backends could only be declared in native VCL. Varnish
 4.0 moved directors from VCL to VMODs, and VMODs can now also create
@@ -107,7 +107,7 @@ documentation.
 
 
 Backend connection timeout
-==========================
+--------------------------
 
 Backend connections will now be closed by Varnish after `backend_idle_timeout`
 seconds of inactivity.
@@ -119,13 +119,13 @@ times, before a working backend connection was found/created.
 
 
 Protocol support
-================
+----------------
 
 Support for HTTP/0.9 on the client side has been retired.
 
 
 More modules available
-======================
+----------------------
 
 Varnish has an ecosystem for third-party modules (vmods). New since
 the last release, these are worth knowing about:
@@ -143,7 +143,7 @@ libvmod-rtstatus: Real time statistics dashboard.
 
 
 Passing data between ESI requests
-=================================
+---------------------------------
 
 A new `req_top` identifier is available in VCL, which is a reference to
 `req` in the top-level ESI request.
@@ -153,7 +153,7 @@ and any ESI sub-requests it leads to.
 
 
 Other noteworthy small changes
-==============================
+------------------------------
 
 * Varnish will now use the ``stale-while-revalidate`` defined in RFC5861
   to set object grace time.

doc/sphinx/whats-new/changes-5.0.rst

+.. _whatsnew_changes_5.0:
+
+Changes in Varnish 5.0
+======================
+
+Varnish 5.0 changes some (mostly) internal APIs and adds som major new
+features over Varnish 4.1.
+
+
+Separate VCL files and VCL labels
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Varnish 5.0 supports jumping from the active VCL's vcl_recv{} to
+another VCL via a VCL label.
+
+The major use of this will probably be to have a separate VCL for
+each domain/vhost, in order to untangle complex VCL files, but
+it is not limited to this criteria, it would also be possible to
+send all POSTs, all JPEG images or all traffic from a certain
+IP range to a separate VCL file.
+
+VCL labels can also be used to give symbolic names to loaded VCL
+configurations, so that operations personel only need to know
+about "normal", "weekend" and "emergency", and web developers
+can update these as usual, without having to tell ops what the
+new weekend VCL is called.
+
+
+Very Experimental HTTP/2 support
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+We are in the process of adding HTTP/2 support to Varnish, but
+the code is very green still - life happened.
+
+But you can actually get a bit of traffic though it already, and
+we hope to have it production ready for the next major release
+(2017-03-15).
+
+Varnish supports HTTP/1 -> 2 upgrade.  For political reasons,
+no browsers support that, but tools like curl does.
+
+For encrypted HTTP/2 traffic, put a SSL proxy in front of Varnish.
+

doc/sphinx/whats-new/index.rst

 .. _whats-new-index:
 
-%%%%%%%%%%%%%%%%%%%%%%%%%%
-What's new in Varnish 4.1
-%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%
+What's new / Upgrading
+%%%%%%%%%%%%%%%%%%%%%%
 
-This section describes the changes that have been made for Varnish 4.1.
+This section describes the changes and improvements between different
+versions of Varnish, and what upgrading between the different versions
+entail.
 
-The first subsection describes overarching changes that have gone into
-Varnish 4.0, while the second subsection describes changes you need to make to
-your current configuration if you come from Varnish 3.x.
+Varnish 5.0
+-----------
 
-The text also considers changes in behaviour that you need to be aware of and
-take into consideration when upgrading.
+.. toctree::
+   :maxdepth: 2
+
+   changes-5.0
+   upgrading-5.0
+
+Varnish 4.1
+-----------
+
+.. toctree::
+   :maxdepth: 2
+
+   changes-4.1
+   upgrading-4.1
+
+Varnish 4.0
+-----------
 
 .. toctree::
    :maxdepth: 2
 
-   changes
-   upgrading
-   upgrade-4.0
+   upgrading-4.0

doc/sphinx/whats-new/upgrade-4.0.rst → doc/sphinx/whats-new/upgrading-4.0.rst

-.. _whatsnew_upgrading:
+.. _whatsnew_upgrading_4_0:
 
 %%%%%%%%%%%%%%%%%%%%%%%%
 Upgrading to Varnish 4.0

doc/sphinx/whats-new/upgrading.rst → doc/sphinx/whats-new/upgrading-4.1.rst

-.. _whatsnew_upgrade41:
+.. _whatsnew_upgrading_4_1:
 
 %%%%%%%%%%%%%%%%%%%%%%%%
 Upgrading to Varnish 4.1

doc/sphinx/whats-new/upgrading-5.0.rst

+.. _whatsnew_upgrading_5_0:
+
+%%%%%%%%%%%%%%%%%%%%%%%%
+Upgrading to Varnish 5.0
+%%%%%%%%%%%%%%%%%%%%%%%%
+
+Changes to VCL
+==============
+
+
+Management interface
+====================
+
+
+Changes to parameters
+=====================
+