Known problems in the 1.38 release

[posvyatokum]

As we transition to the new release process, we will no longer wait for features before the release cut (unless they are vitally important for the network).
This issue now tracks known release problems.
Previous release problem tracking issue: #10376

List of observed issues in 1.38 release

Beta Give feedback

1. -

This a dependancy tracker issue for the 1.38 release. Please, add any features and fixes you want to be included in the release.

[DEPRECATED] Previous issue description

List of required features

Beta Give feedback

1. Feat(near-client): Chunk distribution via message bus #10480
   A-chain C-enhancement Node T-node +4

List of optional features

Beta Give feedback

1. -

[birchmd]

I'd like to see #10480 end up in the release please.

[posvyatokum]

As we are making 1.38.0 release a resharding-only release, we move to a different timeline.
All the features that were added after the 1.37.0 cut will be released in 1.39.0.
Issues to track 1.39 release progress and timeline will be created this week and linked to this issue.

[posvyatokum]

@marcelo-gonzalez added two PRs to master that I want included in 1.38.0 release #10765 #10766

We should ask SRE team to enable state snapshot creation on one of our 1.38.0 split storage and rpc machines as soon as new release is rolled out. This way we can be more sure in the whole snapshot creation process (both correctness and additional space required).