[12389](https://github.com/civicrm/civicrm-core/pull/12389), and
[215](https://github.com/civicrm/civicrm-packages/pull/215))**
- Sites using Redis or Memcache for caching will now use those facilities
- exclusively rather than retaining the `civicrm_cache` table as a backstop.
- This improves performance for these sites, especially those using multiple
- MySQL servers.
+ Sites using Redis or Memcache for caches and sessions will now use those
+ facilities exclusively rather than retaining the `civicrm_cache` table as
+ a backstop. This improves performance for these sites, especially those
+ using multiple MySQL servers.
+
+ As a precaution, Redis or Memcache administrators with very active sites
+ may wish to double-check that they have ample capacity for their caches and
+ sessions.
+
+ For developers, the `CRM_Utils_Cache` APIs now support expiration/TTL
+ times and [PSR-16 CacheInterface](https://www.php-fig.org/psr/psr-16/).
+ The Civi implementation is slightly more permissive than the PSR-16
+ specification; for full compliance, enable `CIVICRM_PSR16_STRICT`.
- **[CRM-21574](https://issues.civicrm.org/jira/browse/CRM-21574) Allow to
disable sending of email from source contact for tell a friend on pcp
- **[dev/core#284](https://lab.civicrm.org/dev/core/issues/284) Aggressive cache
clearing significantly increases test time
- ([12590](https://github.com/civicrm/civicrm-core/pull/12590)) (partial work)**
+ ([12590](https://github.com/civicrm/civicrm-core/pull/12590))**
Settings, compiled Javascript, extension, and other caches are now only
- flushed along with the main CiviCRM cache if an external cache like Redis or
- Memcache is in use.
+ flushed along with the `default` CiviCRM cache if an external cache like Redis or
+ Memcache is in use. (This reproduces the `5.3` behavior.)
- **[dev/core#279](https://lab.civicrm.org/dev/core/issues/279) When Merging two
contacts, Flip between original and duplicate link not working in WordPress