Starting release procedure

Author: hkaiser

CITATION.cff

@@ -7,7 +7,7 @@
 # Metadata for citation of this software according to the CFF format (https://citation-file-format.github.io/)
 cff-version: 1.2.0
 message: If you use this software, please cite it using these metadata.
-title: 'STEllAR-GROUP/hpx: HPX V1.9.1: The C++ Standards Library for Parallelism and
+title: 'STEllAR-GROUP/hpx: HPX V1.10.0: The C++ Standards Library for Parallelism and
   Concurrency'
 doi: 10.5281/zenodo.5185328
 authors:
@@ -84,7 +84,7 @@ authors:
 - given-names: Zahra
   family-names: Khatami
   affiliation: Louisiana State University
-version: 1.9.1
-date-released: 2023-08-04
+version: 1.10.0
+date-released: 2023-10-12
 repository-code: https://github.com/STEllAR-GROUP/hpx
 license: BSL-1.0

CMakeLists.txt

@@ -60,8 +60,8 @@ endif()
 set(HPX_VERSION_MAJOR 1)
 set(HPX_VERSION_MINOR 10)
 set(HPX_VERSION_SUBMINOR 0)
-set(HPX_VERSION_DATE 20230804)
-set(HPX_VERSION_TAG "-trunk")
+set(HPX_VERSION_DATE 20240417)
+set(HPX_VERSION_TAG "-rc1")
 
 set(HPX_VERSION
     "${HPX_VERSION_MAJOR}.${HPX_VERSION_MINOR}.${HPX_VERSION_SUBMINOR}"

cmake/packaging/rpm/Changelog.txt

@@ -1,3 +1,6 @@
+* Wed Apr 17 2024 STE||AR Group <[email protected]> 1.10.0
+- HPX Release 1.10.0 (https://hpx-docs.stellar-group.org/tags/1.10.0/html/releases/whats_new_1_10_0.html)
+
 * Fri Aug 04 2023 STE||AR Group <[email protected]> 1.9.1
 - HPX Release 1.9.1 (https://hpx-docs.stellar-group.org/tags/1.9.1/html/releases/whats_new_1_9_1.html)
 

docs/sphinx/contributing/release_procedure.rst

@@ -1,6 +1,6 @@
 ..
     Copyright (c)      2021 ETH Zurich
-    Copyright (c) 2007-2017 Louisiana State University
+    Copyright (c) 2007-2023 Louisiana State University
 
     SPDX-License-Identifier: BSL-1.0
     Distributed under the Boost Software License, Version 1.0. (See accompanying
@@ -46,14 +46,13 @@ are completed to avoid confusion.
      *   Update collaborators
      *   Update grant information
 
-#. This step does not apply to patch releases. For both APEX and libCDS:
+#. This step does not apply to patch releases. For APEX:
 
    * Change the release branch to be the most current release tag available in
-     the APEX/libCDS ``git_external`` section in the main ``CMakeLists.txt``.
+     the APEX ``git_external`` section in the main ``CMakeLists.txt``.
      Please contact the maintainers of the respective packages to generate a new
      release to synchronize with the |hpx| release (`APEX
-     <https://github.com/UO-OACISS/xpress-apex>`_, `libCDS
-     <https://github.com/STEllAR-GROUP/libcds>`_).
+     <https://github.com/UO-OACISS/xpress-apex>`_).
 
 #. Make sure ``HPX_VERSION_MAJOR/MINOR/SUBMINOR`` in ``CMakeLists.txt`` contain
    the correct values. Change them if needed.
@@ -95,7 +94,7 @@ are completed to avoid confusion.
       The script requires that you have the |stellar| Group signing key.
 
    #. This step is not necessary for patch releases. Notify
-      ``[email protected]`` and ``[email protected]`` of the
+      ``[email protected]`` of the
       availability of the release candidate. Ask users to test the candidate by
       checking out the release candidate tag.
 
@@ -125,9 +124,8 @@ are completed to avoid confusion.
    script automatically tag the with the corresponding release number. The
    script requires that you have the |stellar| Group signing key.
 
-#. Update the websites (`hpx.stellar-group.org <https://hpx.stellar-group.org>`_,
-   `stellar-group.org <https://stellar-group.org>`_ and
-   `stellar.cct.lsu.edu <https://stellar.cct.lsu.edu>`_). You can login on
+#. Update the websites (`hpx.stellar-group.org <https://hpx.stellar-group.org>`_
+   and `stellar-group.org <https://stellar-group.org>`). You can login on
    wordpress through `this page <https://hpx.stellar-group.org/wp-login.php>`.
    You can update the pages with the following:
 

docs/sphinx/quickstart.rst

@@ -156,7 +156,7 @@ distributed applications similarly to how you would write applications for a
 single node (see :ref:`why_hpx` and
 :ref:`writing_distributed_hpx_applications`).
 
-If you are already familiar with ``async`` and ``future``\ s from the C++ standard
+If you are already familiar with ``async`` and ``future`` from the C++ standard
 library, the same functionality is available in |hpx|.
 
 The following terminology is essential when talking about task-based C++