Prep v1.2.2 release

Author: shuds13

.wci.yml

@@ -16,8 +16,8 @@ description: |
 language: Python
 
 release:
-  version: 1.2.1
-  date: 2024-02-23
+  version: 1.2.2
+  date: 2024-03-22
 
 documentation:
   general: https://libensemble.readthedocs.io

CHANGELOG.rst

@@ -8,6 +8,29 @@ GitHub issues are referenced, and can be viewed with hyperlinks on the `github r
 
 .. _`github releases page`: https://github.com/Libensemble/libensemble/releases
 
+Release 1.2.2
+--------------
+
+:Date: March 22, 2024
+
+* Bugfix: Some `libE_specs` were not passed through correctly when added after ensemble initialization. #1264
+* `platform_specs` options are merged with detected platforms, rather than replacing. #1265
+* Ensure simulations directories are created when `sim_input_dir` is specified, likewise for gen dirs. #1266
+
+Example user functions:
+
+* Improved structure of gpCAM generator. #1260
+
+:Note:
+
+* Tests were run on Linux and MacOS with Python versions 3.9, 3.10, 3.11, 3.12
+* Heterogeneous workflows tested on Aurora (ALCF), Frontier (OLCF), Polaris, and Perlmutter (NERSC).
+* Tests were also run on Bebop and Improv LCRC systems.
+
+:Known Issues:
+
+* See known issues section in the documentation.
+
 Release 1.2.1
 --------------
 

docs/dev_guide/release_management/release_platforms/rel_spack.rst

@@ -10,8 +10,7 @@ This assumes you have already:
 
 Details on how to create forks can be found at https://help.github.com/articles/fork-a-repo.
 
-You now have a configuration like that shown at (but without the upstream/local connection).
-https://stackoverflow.com/questions/6286571/are-git-forks-actually-git-clones.
+You now have a configuration like that shown at https://stackoverflow.com/a/6286877/6346040.
 
 Upstream, in this case, is the official Spack repository on GitHub. Origin is
 your fork on GitHub, and Local Machine is your local clone (from your fork).
@@ -54,16 +53,17 @@ Fetch from the upstream repo::
 To update your local machine, you may wish to rebase or overwrite your local files.
 Select from the following:
 
-If you have local changes to go "on top" of latest code::
+Now make your local machine identical to upstream repo (**WARNING:** Any local changes will be lost!)::
 
-    git rebase upstream/develop
+    git reset --hard upstream/develop
 
-Or to make your local machine identical to upstream repo (**WARNING:** Any local changes will be lost!)::
+Alternativvely, if you have existing local changes to go "on top" of latest code (usually we will
+make our release updates after this)::
 
-    git reset --hard upstream/develop
+    git rebase upstream/develop
 
 (Optional) You may want to update your forked (origin) repo on GitHub at this point.
-This may requires a forced push::
+This may require a forced push::
 
     git push origin develop --force
 
@@ -106,9 +106,9 @@ This will install a few python spack packages and run style checks on just
 your changes. Make adjustments if needed, until this passes.
 
 If okay - add, commit, and push to origin (forked repo). For example, if your version
-number is 0.9.1::
+number is 1.2.2::
 
-     git commit -am "libEnsemble: add v0.9.1"
+     git commit -am "libEnsemble: add v1.2.2"
      git push origin develop --force
 
 Once the branch is pushed to the forked repo, go to GitHub and do a pull request from this

libensemble/version.py

@@ -1 +1 @@
-__version__ = "1.2.1+dev"
+__version__ = "1.2.2"