doc: Move the release notes to 6.5

doc/sphinx/whats-new/changes-trunk.rst → doc/sphinx/whats-new/changes-6.5.rst

-**Note: This is a working document for a future release, with running
-updates for changes in the development branch. For changes in the
-released versions of Varnish, see:** :ref:`whats-new-index`
+.. _whatsnew_changes_6.5:
 
-.. _whatsnew_changes_CURRENT:
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-Changes in Varnish **$NEXT_RELEASE**
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%
+Changes in Varnish 6.5.0
+%%%%%%%%%%%%%%%%%%%%%%%%
 
 For information about updating your current Varnish deployment to the
-new version, see :ref:`whatsnew_upgrading_CURRENT`.
+new version, see :ref:`whatsnew_upgrading_6.5`.
 
 A more detailed and technical account of changes in Varnish, with
 links to issues that have been fixed and pull requests that have been
@@ -171,7 +167,7 @@ VMOD authors who would like to generate VCC files can now use the
 ``VARNISH_VMODS_GENERATED()`` macro from ``varnish.m4`` for autotools
 builds.
 
-.. _whatsnew_changes_CURRENT_workspace:
+.. _whatsnew_changes_6.5_workspace:
 
 Workspace API
 ~~~~~~~~~~~~~
@@ -200,7 +196,7 @@ Other VRT / cache.h changes
 
 * Added ``VRT_BLOB_string()`` for the default BLOB folding documented above
 
-.. _whatsnew_changes_CURRENT_vsc:
+.. _whatsnew_changes_6.5_vsc:
 
 libvarnishapi
 ~~~~~~~~~~~~~
@@ -219,7 +215,7 @@ they are all tested in order and the first to match determines the outcome.
 The ``'R'`` argument takes precedence over regular filtering and can be used
 to ensure that some counters are present regardless of user configuration.
 
-.. _whatsnew_changes_CURRENT_libvarnish:
+.. _whatsnew_changes_6.5_libvarnish:
 
 libvarnish
 ~~~~~~~~~~

doc/sphinx/whats-new/index.rst

@@ -8,18 +8,14 @@ This section describes the changes and improvements between different
 versions of Varnish, and what upgrading between the different versions
 entail.
 
-Varnish **$NEXT_RELEASE**
--------------------------
-
-**Note: These are working documents for a future release, with running
-updates for changes in the development branch. For changes in the
-released versions of Varnish, see the chapters listed below.**
+Varnish 6.5
+-----------
 
 .. toctree::
    :maxdepth: 2
 
-   changes-trunk
-   upgrading-trunk
+   changes-6.5
+   upgrading-6.5
 
 Varnish 6.4
 -----------

doc/sphinx/whats-new/upgrading-trunk.rst → doc/sphinx/whats-new/upgrading-6.5.rst

-**Note: This is a working document for a future release, with running
-updates for changes in the development branch. For changes in the
-released versions of Varnish, see:** :ref:`whats-new-index`
+.. _whatsnew_upgrading_6.5:
 
-.. _whatsnew_upgrading_CURRENT:
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-Upgrading to Varnish **$NEXT_RELEASE**
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%
+Upgrading to Varnish 6.5.0
+%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 varnishstat
 ===========
@@ -64,7 +60,7 @@ VSB
 
 VSB support for dynamic vs. static allocations has been changed and
 code using VSBs will need to be adjusted, see
-:ref:`whatsnew_changes_CURRENT_libvarnish`.
+:ref:`whatsnew_changes_6.5_libvarnish`.
 
 It should be noted that the VSB itself and the string buffer must be either
 both dynamic or both static. It is no longer possible for example to have
@@ -74,7 +70,7 @@ Workspace API
 ~~~~~~~~~~~~~
 
 VMODs using the Workspace API might need minor adjustments, see
-:ref:`whatsnew_changes_CURRENT_workspace`.
+:ref:`whatsnew_changes_6.5_workspace`.
 
 In general, accessing any field of ``struct ws`` is strongly discouraged
 and if the workspace API doesn't satisfy all your needs please bring
@@ -84,7 +80,7 @@ VSC
 ~~~
 
 The ``'f'`` argument for ``VSC_Arg()`` is now deprecated as mentioned in
-the above note on `varnishstat`_ and :ref:`whatsnew_changes_CURRENT_vsc`.
+the above note on `varnishstat`_ and :ref:`whatsnew_changes_6.5_vsc`.
 
 Otherwise you can use the ``'I'`` ans ``'X'`` arguments to respectively
 include or exclude counters, they work in a first-match fashion. Since