3.7.0 changelog and release

[noissue]
pulp · Sep 24, 2020 · acd5755 · acd5755
1 parent 2dee659
commit acd5755
Show file tree

Hide file tree

Showing 8 changed files with 43 additions and 17 deletions.
diff --git a/CHANGES/6988.feature b/CHANGES/6988.feature
diff --git a/CHANGES/7499.bugfix b/CHANGES/7499.bugfix
diff --git a/CHANGES/7516.dev b/CHANGES/7516.dev
diff --git a/CHANGES/7517.dev b/CHANGES/7517.dev
diff --git a/docs/CHANGES.md b/docs/CHANGES.md
@@ -13,6 +13,37 @@ Changelog
 
 <!-- TOWNCRIER -->
 
+3.7.0 (2020-09-23)
+==================
+
+
+Features
+--------
+
+- Install patched dependencies that are modified for FIPS compatibility on Red Hat based operating systems. Additionally remove ``md5`` from the ``ALLOWED_CONTENT_CHECKSUMS`` setting. Users can override the ``ALLOWED_CONTENT_CHECKSUMS`` if a new value is provided.
+  [#6988](https://pulp.plan.io/issues/6988)
+
+
+Bugfixes
+--------
+
+- Changed the mechanism to only set the admin password on first installation.
+  Removed the depedency of ``pulp_health_check`` on the variable ``pulp_default_admin_password``.
+  [#7499](https://pulp.plan.io/issues/7499)
+
+
+Devel
+-----
+
+- pulp_devel role now installs distro-specific packages in parallel, for better performance when run against hosts running multiple distros (like our molecule CI).
+  [#7516](https://pulp.plan.io/issues/7516)
+- pulp_installer's CI/molecule "packages mode" tests now test a new Foreman/Katello project URL for RPM packages. Has pulpcore 3.6 rather than 3.4.
+  [#7517](https://pulp.plan.io/issues/7517)
+
+
+----
+
+
 3.6.3-1 (2020-09-15)
 ====================
 

diff --git a/docs/index.md b/docs/index.md
@@ -5,9 +5,9 @@ The Pulp 3 Ansible installer is a collection of Ansible roles that you can use t
 
 Each Ansible role installs and configures a component of Pulp.
 
-This version of the installer, 3.6.3-1, installs Pulp 3.6.3 specifically.
+This version of the installer, 3.7.0, installs Pulp 3.7.0 specifically.
 
-If run against an older version of Pulp 3, it will upgrade it to 3.6.3.
+If run against an older version of Pulp 3, it will upgrade it to 3.7.0.
 
 System Requirements
 -------------------
@@ -89,18 +89,18 @@ Recommended Workflows for Pulpcore & Plugin Versioning
 Initial installation:
 
 1. Make sure you are running the latest version of the installer, which installs the latest version
-   of pulpcore (3.6.3).
+   of pulpcore (3.7.0).
 1. Confirm that all the latest stable releases of your desired plugins are compatible with pulpcore
-   3.6.3, such as by reading the release announcement email thread for pulpcore 3.6.3, reading the
+   3.7.0, such as by reading the release announcement email thread for pulpcore 3.7.0, reading the
 plugins README, or as a last resort, reading their `setup.py`.
 1. Run `pulp_installer`.
 
 Upgrading your installation:
 
 1. Observe what is the latest version of `pulp_installer`, and what version of pulpcore it installed
-   (3.6.3).
+   (3.7.0).
 1. Confirm that all the latest stable releases of **currently installed** plugins are compatible
-   with pulpcore 3.6.3, such as by reading the release announcement email thread for pulpcore 3.6.3,
+   with pulpcore 3.7.0, such as by reading the release announcement email thread for pulpcore 3.7.0,
 reading the plugins README, or as a last resort, reading their setup.py.
 1. If they are not all compatible yet, **wait** for the plugins to be updated for
    compatibility.
@@ -112,9 +112,9 @@ reading the plugins README, or as a last resort, reading their setup.py.
 
 Initial installation:
 
-1. Observe the latest branch of `pulp_installer`, and what version of pulpcore it installs (3.6.3).
+1. Observe the latest branch of `pulp_installer`, and what version of pulpcore it installs (3.7.0).
 1. Confirm that all the latest stable releases of your desired plugins are compatible with pulpcore
-   3.6.3, such as by reading the release announcement email thread for pulpcore 3.6.3, reading the
+   3.7.0, such as by reading the release announcement email thread for pulpcore 3.7.0, reading the
 plugins README, or as a last resort, reading their setup.py.
 1. If they are not all compatible yet, try the last version of the installer that installs pulpcore
    3.3.z . Then confirm that there exist stable releases of your desired plugins that are compatible
@@ -126,9 +126,9 @@ with pulpcore 3.3.z. If there are none, try pulpcore 3.2.z, and repeate.
 Upgrading your install:
 
 1. Observe what the latest version of `pulp_installer` is, and what version of pulpcore it installed
-   (3.6.3). (Even if there is no update, you can still upgrade your plugins.)
+   (3.7.0). (Even if there is no update, you can still upgrade your plugins.)
 1. Confirm that all the latest stable releases of **currently installed** plugins are compatible
-   with pulpcore 3.6.3, such as by reading the release announcement email thread for pulpcore 3.6.3,
+   with pulpcore 3.7.0, such as by reading the release announcement email thread for pulpcore 3.7.0,
 reading the plugins README, or as a last resort, reading their setup.py.
 1. If they are not all compatible yet, try the last version of the installer that installs pulpcore
    3.3.z . Then confirm that there exist stable releases of your desired plugins that are compatible

diff --git a/galaxy.yml b/galaxy.yml
@@ -10,7 +10,7 @@ namespace: pulp
 name: pulp_installer
 
 # The version of the collection. Must be compatible with semantic versioning
-version: 3.6.3-1
+version: 3.7.0
 
 # The path to the Markdown (.md) readme file. This path is relative to the root of the collection
 readme: README.md

diff --git a/roles/pulp_common/defaults/main.yml b/roles/pulp_common/defaults/main.yml
@@ -14,7 +14,7 @@ pulp_upgrade: false
 #  they are confident that this version of pulp_installer is compatible with
 #  pulp_version.
 #  Ignored if pulp_source_dir is set
-pulp_version: "3.6.3"
+pulp_version: "3.7.0"
 pulp_user: pulp
 pulp_user_id:
 pulp_group: pulp