Update cookbooks and add wordpress cookbook

cookbooks/postgresql/CHANGELOG.md

@@ -2,11 +2,42 @@ postgresql Cookbook CHANGELOG
 =============================
 This file is used to list changes made in each version of the postgresql cookbook.
 
+v4.0.0
+-----
+* Potential breaking change: Restructured default attributes to avoid compile time deriving other attribute values from value of the `node[‘postgresql’][‘version’]`
+(#313, #302, #295, #288, #280, #261, #260, #254, #248, #217, #214, #167, #143)
+* Correct issues which caused the inability to override installation version defaults
+* Correct issues which caused configuration file entries with miss matching version numbers and incorrect file system paths being defined
+* Remove method pgdgrepo_rpm_info compile time use of derived attributes case many issues
+* Use correct directory path and check for the correct not_if condition to determine if the database has been initialized
+* Ensure that correct packages are installed in all scenarios where pg gem is compiled
+* Fix errors in configuration files for unix_socket_directory and unix_socket_directories
+* Updates to test-kitchen suite configuration
+* Added more grey hair to my beard
+
+v3.4.24
+-------
+* Corrections to address repositories signed with newer certificates that some distributions have in their default ca-certificates package
+* Updates to more accurately determine distributions service init systems adds better support for systemd systems
+* Correct how version attribute is evaluated in certain places
+* test-kitchen suite configuration corrections
+* Opensuse support
+
+v3.4.23
+-------
+- Skipping 3.4.22 with Develop branch 3.4.23 to return to releasing cookbook from master on even numbers and develop on odd numbers.
+
+v3.4.21
+-------
+- Use more optimistic openssl version constraint
+- Add Postgresql 9.4 package sources for RHEL platforms
+- Update testing infrastructure to address bit rot
+
 v3.4.20
 -------
 - Revert [#251](https://github.com/hw-cookbooks/postgresql/pull/251), a change which caused the postgresql service to restart every Chef run.
 
-v3.4.19 [YANKED]
+v3.4.19
 -------
 - node.save could better not be run on every chef run since it causes node.default attributes stored to the node objects to differ during a chef run and when
 - Missing attribute in docs for yum_pgdg_postgresql