v1.14: rolls out merkle shreds to ~5% of mainnet slots (backport of #32337)

[mergify]

This is an automatic backport of pull request #32337 done by Mergify.
Cherry-pick of 43a5ed3 has failed:

On branch mergify/bp/v1.14/pr-32337
Your branch is up to date with 'origin/v1.14'.

You are currently cherry-picking commit 43a5ed3139.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   core/src/broadcast_stage/standard_broadcast_run.rs

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[jbiseda]

I thought v1.14 backports were limited to critical fixes. @willhickey

[behzadnouri]

I thought v1.14 backports were limited to critical fixes. @willhickey

Merkle shreds are already shipped in v1.14.
The commit starts the incremental rollout process.

[willhickey]

Merkle shreds are already shipped in v1.14. The commit starts the incremental rollout process.

I would rather avoid the cluster-specific code and have identical logic progress through testnet stabilization before going to mainnet-beta.

I think you've explained this before but I can't find it on Discord... is the rollout plan written down somewhere?

[behzadnouri]

Merkle shreds are already shipped in v1.14. The commit starts the incremental rollout process.

I would rather avoid the cluster-specific code and have identical logic progress through testnet stabilization before going to mainnet-beta.

I think you've explained this before but I can't find it on Discord... is the rollout plan written down somewhere?

We went 5% -> 20% -> 100% rollout on testnet: #28199, #28905, #32316
and this commit starts replicating the same process on mainnet.

[codecov]

Codecov Report

Merging #32347 (b79b1c9) into v1.14 (87ce9bb) will increase coverage by 0.0%.
The diff coverage is 75.0%.

@@           Coverage Diff           @@
##            v1.14   #32347   +/-   ##
=======================================
  Coverage    82.1%    82.1%           
=======================================
  Files         665      665           
  Lines      185418   185421    +3     
=======================================
+ Hits       152325   152340   +15     
+ Misses      33093    33081   -12     

[willhickey]

Approved for v1.14 backport