Merge beta 21.3.0.2 into trunk

[mokagio]

Includes:

• Track Load WordPress screen events and content export events by @salimbraksa
• [Jetpack Content Migration] Enable Content Migration Flow by @twstokes
• CMF: Don't present the flow when feature flag is disabled by @dvdchr
• [Jetpack Content Migration] Disable Content Migration Flow by @twstokes
• [Jetpack Content Migration Flow] Put the ContentMigrationCoordinator behind feature flag by @twstokes
• Update WordPress 21.3 release notes with Jetpack migration by @mokagio
• [Jetpack Focus] Revert Jetpack Notifications Disabling Feature Flag and Release Notes by @staskus

@twstokes 🤔 I'm not sure at this point whether my amendment of the release notes should be considered valid, in light of the feature flag? Maybe better to remove it? Thanks!

I'm aware we might not ship 21.3, but just want to have the state in the codebase internally consistent. Also, if we revert my change before merging, we'll avoid confusion with the translators.

[wpmobilebot]

You can test the changes in Jetpack from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr19742-fa14718 on your iPhone

If you need access to App Center, please ask a maintainer to add you.

[wpmobilebot]

You can test the changes in WordPress from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr19742-fa14718 on your iPhone

If you need access to App Center, please ask a maintainer to add you.

[twstokes]

but just want to have the state in the codebase internally consistent. Also, if we revert my change before merging, we'll avoid confusion with the translators.

Hey 👋 @mokagio - those sound like good reasons to me to revert the commit. Good catch. 👍

If I should open a PR to revert it just let me know. 🙇

[mokagio]

If I should open a PR to revert it just let me know. 🙇

No need, done in 27964b2.

Sorry, I was only looking for your confirmation I didn't mean to suggest you'd have to make the change.

[twstokes]

This looks great @mokagio! 🙇

We're really close to merging #19735 (just waiting for all green tests). Would it be more efficient to include it on this merge, or is it better to wait?

Well, I may have answered my own question by merging the branch. 😬 Sorry if this complicated things. I've added #19735 to the description of this PR.

[peril-wordpress-mobile]

	Messages
📖	This PR has the 'Releases' label: some checks will be skipped.

Generated by 🚫 dangerJS

[mokagio]

@twstokes, no worries! 😄

Would it be more efficient to include it on this merge, or is it better to wait?

From the point of view of getting the changes into trunk, merging here is the most efficient thing to do because it'll mean we won't have to do another dedicated PR for it.

However, from the point of view of having a beta with those changes, merging the code will not trigger a new beta deployment. That is a process release managers (or anyone with the right tokens in their environment) trigger manually via bundle exec fastlane new_beta_release.

If you'd like a new beta with these changes, it'd be straightforward to make one but I'd suggest waiting until tomorrow (or ~12-24 hours) so that we can get more translations in.

[twstokes]

@twstokes, no worries! 😄

Would it be more efficient to include it on this merge, or is it better to wait?

From the point of view of getting the changes into trunk, merging here is the most efficient thing to do because it'll mean we won't have to do another dedicated PR for it.

However, from the point of view of having a beta with those changes, merging the code will not trigger a new beta deployment. That is a process release managers (or anyone with the right tokens in their environment) trigger manually via bundle exec fastlane new_beta_release.

Whew, thanks a bunch @mokagio.