Proposed version 2.2.2

[ximinez]

High Level Overview of Change

This is a hotfix release that fixes a ongoing issue on Mainnet where a majority of UNL validators will stall during consensus processing due to lock contention, preventing ledgers from being validated for up to two minutes.

The base branch is master. This PR will be merged with --ff-only (not squashed or rebased, and not using the GitHub UI) to master, and reverse-merged to develop. Do not use the Github UI to merge this PR

---

This PR / branch is identical to #5106, which is currently being tested, with two exceptions:

• The version number is updated
• The commits are reorganized and "cleaned up" for release.

$ git fetch origin && git diff origin/pr/2.2.2-rc1 origin/master-next 
diff --git a/src/ripple/protocol/impl/BuildInfo.cpp b/src/ripple/protocol/impl/BuildInfo.cpp
index 44aef03533..0086824b7e 100644
--- a/src/ripple/protocol/impl/BuildInfo.cpp
+++ b/src/ripple/protocol/impl/BuildInfo.cpp
@@ -33,7 +33,7 @@ namespace BuildInfo {
 //  and follow the format described at http://semver.org/
 //------------------------------------------------------------------------------
 // clang-format off
-char const* const versionString = "2.2.2-rc2"
+char const* const versionString = "2.2.2"
 // clang-format on
 
 #if defined(DEBUG) || defined(SANITIZER)

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Release

[Bronek]

LGTM

[mDuo13]

This PR should edit RELEASENOTES.md to add the new release.

The changes can be relatively small. The opening sentence of this PR is good for the overview.

[ximinez]

This PR should edit RELEASENOTES.md to add the new release.

The changes can be relatively small. The opening sentence of this PR is good for the overview.

I saw this after merging the PR. Do you think we'd be ok adding release notes when we reverse merge into develop?

[WietseWind]

FYI @ximinez @mtrippled - this seems to make a difference on FH nodes @ xrplcluster - less transitions, less hiccups in ledger steram over websocket.

Installed it on half the machines and the ones with 2.2.2 definitely seem to do significantly better.

[ximinez]

This is great news, @WietseWind ! Thanks for the update!