Updating version number for 2.6.5 patch release

CMakeLists.txt

@@ -10,7 +10,7 @@ project (APEX CXX C)
 set (APEX_DESCRIPTION "Autonomic Performance Environment for eXascale" CACHE STRING "APEX project description")
 set (APEX_VERSION_MAJOR 2 CACHE STRING "APEX Major Version")
 set (APEX_VERSION_MINOR 6 CACHE STRING "APEX Minor Version")
-set (APEX_VERSION_PATCH 4 CACHE STRING "APEX Patch Version")
+set (APEX_VERSION_PATCH 5 CACHE STRING "APEX Patch Version")
 set (APEX_HOMEPAGE_URL "http://github.com/UO-OACISS/apex" CACHE STRING "APEX homepage URL")
 
 cmake_policy(VERSION 2.8.12)

doc/Doxyfile.in

@@ -38,7 +38,7 @@ PROJECT_NAME           = "Autonomic Performance Environment for eXascale (APEX)"
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 2.6.4
+PROJECT_NUMBER         = 2.6.5
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

doc/webdocs/docs/install.md

@@ -8,7 +8,7 @@ APEX is integrated into the [HPX runtime](https://hpx.stellar-group.org), and is
 -DHPX_WITH_APEX=TRUE
 ```
 
-The `-DHPX_WITH_APEX_TAG=develop` can be used to indicate a specific release version of APEX, or to use a specific GitHub branch of APEX.  We recommend using the default configured version that comes with HPX (currently `v2.6.4`) or the `develop` branch.  Additional CMake flags include:
+The `-DHPX_WITH_APEX_TAG=develop` can be used to indicate a specific release version of APEX, or to use a specific GitHub branch of APEX.  We recommend using the default configured version that comes with HPX (currently `v2.6.5`) or the `develop` branch.  Additional CMake flags include:
 
 * `-DAPEX_WITH_LM_SENSORS=TRUE` to enable [LM sensors](https://hwmon.wiki.kernel.org/lm_sensors) support (assumed to be installed in default system paths)
 * `-DAPEX_WITH_PAPI=TRUE` and `-DPAPI_ROOT=...` to enable [PAPI](https://icl.utk.edu/papi/) support
@@ -23,12 +23,12 @@ The `-DHPX_WITH_APEX_TAG=develop` can be used to indicate a specific release ver
 
 APEX is open source, and available on Github at <http://github.com/UO-OACISS/apex>.
 
-For stability, most users will want to download [the most recent release](https://github.com/UO-OACISS/apex/releases) of APEX (for example, v2.6.4):
+For stability, most users will want to download [the most recent release](https://github.com/UO-OACISS/apex/releases) of APEX (for example, v2.6.5):
 
 ```bash
-wget https://github.com/UO-OACISS/apex/archive/refs/tags/v2.6.4.tar.gz
-tar -xvzf v2.6.4.tar.gz
-cd apex-2.6.4
+wget https://github.com/UO-OACISS/apex/archive/refs/tags/v2.6.5.tar.gz
+tar -xvzf v2.6.5.tar.gz
+cd apex-2.6.5
 ```
 
 Other users may want to work with the most recent code available, in which case you can clone the git repo:
@@ -153,7 +153,7 @@ The process for building APEX is:
 2) Enter the repo directory:
 
 ```bash
-cd apex-2.6.4
+cd apex-2.6.5
 ```
 
 3) configure using CMake:

src/apex/CMakeLists_hpx.cmake

@@ -19,7 +19,7 @@ hpx_info("apex" "Will build APEX")
 
 set (APEX_VERSION_MAJOR 2)
 set (APEX_VERSION_MINOR 6)
-set (APEX_VERSION_PATCH 4)
+set (APEX_VERSION_PATCH 5)
 
 if (NOT APEX_ROOT)
   if (EXISTS ${HPX_SOURCE_DIR}/apex)

src/scripts/make_release.txt

@@ -1,6 +1,6 @@
 0) Update develop and master, merge develop into master
 
-update the version number in CMakeLists.txt, src/apex/CMakeLists.hpx and doc/Doxyfile.in
+update the version number in CMakeLists.txt, src/apex/CMakeLists.hpx and doc/Doxyfile.in and docs/webdocs/install.md
 
 git checkout develop
 git pull