Document releases flow

[Saadnajmi]

Please select one of the following

• I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
• I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
• I am making a fix / change for the macOS implementation of react-native
• I am making a change required for Microsoft usage of react-native

Summary

Update the Releases.md doc with actual info

Changelog

[GENERAL] [ADDED] - Update the Releases.md doc with actual info

Test Plan

N/A

[kelset]

done some tweaks, and left some questions: I'm not sure I fully understand the process but it sounds like this process of releasing a new version gets triggered for every new commit that lands in a -stable branch?

We could use some clarity also around nightlies, are they actually working? Which branch do they get built from?

[lunaleaps]

Might be useful to have this diagram of core React Native release flows:

[kelset]

@lunaleaps: headsup - this is a PR for the macos repo about the macos release flow; I guess we need that release graph in some "release documentation flow" upstream for core too, but let's make sure to not confuse things ;)

[Saadnajmi]

done some tweaks, and left some questions: I'm not sure I fully understand the process but it sounds like this process of releasing a new version gets triggered for every new commit that lands in a -stable branch?

We could use some clarity also around nightlies, are they actually working? Which branch do they get built from?

Yes, releases get triggered for every new commit that lands on a stable branch. Nightlies are triggered for every new commit that lands on the main branch. Since that isn't actually a nightly (it doesn't happen once a night), the npm dist-tag is canary. And yes they are working.

[Saadnajmi]

@lunaleaps: headsup - this is a PR for the macos repo about the macos release flow; I guess we need that release graph in some "release documentation flow" upstream for core too, but let's make sure to not confuse things ;)

I'm going to elect to not include that graphic in the React Native macOS release doc, so as to not cause confusion. If that graphic is in the React Native repo / at a publicly accessible link, I can link it :)

[Saadnajmi]

done some tweaks, and left some questions: I'm not sure I fully understand the process but it sounds like this process of releasing a new version gets triggered for every new commit that lands in a -stable branch?

We could use some clarity also around nightlies, are they actually working? Which branch do they get built from?

I committed all your suggestions and added a few lines to the top clarifying the 3 types of builds we have and when they get released. I hope that helps clarify about nightlies.

[kelset]

left a few more comments, overall it's almost ready to go I think.
A future improvement would be a section on "cutting a new minor" with details on how that should be handled.

[lunaleaps]

headsup - this is a PR for the macos repo about the macos release flow; I guess we need that release graph in some "release documentation flow" upstream for core too, but let's make sure to not confuse things ;)

Yup I'm aware! Was sharing the graph for context on the "Relevant scripts from React native core" section because there was some in-accuracies.

... We aren't synced to paste monorepo work just yet, so I will probably leave a note to say this changes for 0.72+.

The mono-repo doesn't actually change much of this flow. It's mostly scripts about bumping and publishing packages that aren't react-native and aren't private.

Getting this into react-native release docs

Agreed, we should add it!