Merge branch 'develop' into tracing-progress-review

Author: boegel

.github/workflows/test.yml

@@ -22,7 +22,7 @@ jobs:
         uses: codespell-project/actions-codespell@master
         with:
           check_filenames: true
-          ignore_words_list: atleast,ninjs,simpy,proovread,namd,precice,crate
+          ignore_words_list: atleast,ninjs,simpy,proovread,namd,precice,crate,ake
           # filter out
           #   docs/js/asciinema-player-2.6.1.js as it is not markdown
           #   version-specific/supported-software.md as the software descriptions have spelling errors

docs/policies/toolchains.md

@@ -0,0 +1,33 @@
+# Supported Toolchain Generations Policy {: #policy_toolchains }
+
+!!! note
+     This policy will be implemented as part of the release of [EasyBuild 5.0][overview]
+
+For the central EasyBuild repositories, we support a set of toolchain generations.
+
+* Accept PRs only for the 6 most recent toolchain generations.
+* Deprecate toolchains generations 7 and 8, including closing PRs and issues for these toolchains.
+* Archive easyconfigs using toolchain generation 9 (and older).
+
+## Notes
+
+* This assumes we continue with two toolchain generations per year.
+* A toolchain generation exists when we have an lettered (i.e. 2024a) toolchain in `develop`.
+
+## Background
+
+The central easyconfigs repository is intended to provide references easyconfigs. For the reference easyconfigs we
+aim to have only one version of a software being used as a dependency in each toolchain generation. (There are
+exceptions, but we aim to keep these limited.)
+
+Sites and users can then supplement these easyconfigs via there own collection of easyconfigs. This additional
+collection is added via the [robot search path][robot_search_path].
+
+## Example
+
+As of November 2023 the latest toolchain generation is `2023b`.
+
+* Supported: 2023b, 2023a, 2022b, 2022a, 2021b, 2021a
+* Deprecated: 2020b and 2020a
+* Archived (and unsupported): 2019b and older
+

docs/removed-functionality.md

@@ -50,7 +50,7 @@ fittingly named `use_fma4` parameter in EasyBuild v3.2.0.
 - *alternatives*: **use** `extract_cmd` **key in Python dictionary
     format instead**
 
-Specyfing a custom extraction command for a particular source file by
+Specifying a custom extraction command for a particular source file by
 using a 2-element tuple in `sources` is no longer supported.
 
 Instead, a Python dictionary containing the `filename` and `extract_cmd`

docs/version-specific/eb-help.md

@@ -283,7 +283,7 @@ Option flag                                                              |Option
 ``--optarch=OPTARCH``                                                    |Set architecture optimization, overriding native architecture optimizations
 ``--output-format=OUTPUT-FORMAT``                                        |Set output format (type choice; default: txt) (choices: md, rst, txt)
 ``--output-style=OUTPUT-STYLE``                                          |Control output style; auto implies using Rich if available to produce rich output, with fallback to basic colored output (type choice; default: auto) (choices: auto, basic, no_color, rich)
-``--parallel=PARALLEL``                                                  |Specify (maximum) level of parallellism used during build procedure (type int)
+``--parallel=PARALLEL``                                                  |Specify (maximum) level of parallelism used during build procedure (type int)
 ``--parallel-extensions-install``                                        |Install list of extensions in parallel (if supported) (default: False)
 ``--pre-create-installdir``                                              |Create installation directory before submitting build jobs (default: True; disable with --disable-pre-create-installdir)
 ``-p, --pretend``                                                        |Does the build/installation in a test directory located in $HOME/easybuildinstall (default: False)