Release checklist (2024-06-19)
Go through the checkboxes below and tick off your assigned ones, in sequence. If a bug is found and a previous step is restarted, all subsequent checkboxes must be done again.
Example: a bug is found when verifying the very last feature of the release candidate. A bugfix is created, a new RC tag is created, the tag is logged at the top of the checklist as a new checkmark. All other features must also be verified again with the latest RC release.
-
Tag release candidate version 4.0.0rc1. @matejart -
Verify the features work correctly on the release candidate: -
I can run spotter scan get > config.json || spotter scan set config.json
without seeing an error at the second step. -
I can take my execution environment YAML definition file to build a new execution environment using spotter build --file ee.yml
a working container with the execution environment for my playbooks. -
Spotter's scan payload now contains: -
dynamic_inventories
. -
roles
. -
module_defaults
.
-
-
If I scan with --exclude-metadata
, thelocation
fields of theinstalled_collections
and theinstalled_roles
entries in the exported payload are all set tonull
.
-
-
Approve that no changes need to be added to this release @gregor.berginc -
Changelog is up to date. @matejart -
Assign production version 4.0.0 to the commit previously tagged as RC. @matejart
/cc @gregor.berginc
Edited by Matej Artač