Cleanup of docs post 0.74 release (#756)

Co-authored-by: Riccardo Cipolleschi <[email protected]>

Author: cortinico

.github/ISSUE_TEMPLATE/release_checklist.yml

@@ -18,7 +18,7 @@ body:
     attributes:
       label: Target Minor
       description: Release Minor (for auto-triaging).
-      placeholder: "0.74"
+      placeholder: "0.77"
     validations:
       required: true
 
@@ -32,10 +32,8 @@ body:
 
         - [ ] [Complete picks](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process-0.73.md#step-2-cherry-pick-or-merge-requests-against-release-branch)
           - See [framework to evaluate priority of picks](https://github.com/reactwg/react-native-releases/blob/main/docs/support.md#release-issues-and-pick-request-escalation)
-        - [ ] (If < 0.74) [Publish monorepo packages](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process-0.73.md#step-3-publish-monorepo-packages)
-        - [ ] [Push things remote to get assets (like Hermes) ready](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process-0.73.md#step-4-build-artifacts-on-circleci)
+        - [ ] [Push things remote to get assets (like Hermes) ready](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process.md#step-4-build-artifacts-on-circleci)
         - [ ] Test release (create [Test Report](https://github.com/reactwg/react-native-releases/issues/new/choose))
-        - [ ] (If > 0.74) [Publish monorepo packages](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process-0.73.md#step-6-publish-monorepo-packages)
         - [ ] [Publish `react-native`](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process-0.73.md#step-7-publish-react-native)
         - [ ] [Verify release](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process-0.73.md#step-8-verify-release)
         - [ ] [Update Changelog](https://github.com/reactwg/react-native-releases/blob/main/docs/guide-release-process-0.73.md#step-9-generate-the-changelog-pr)

README.md

@@ -5,6 +5,7 @@ This repository is dedicated to coordinating React Native releases. It contains
 ## Pick Requests and Support Policy
 
 ### What is a pick request?
+
 A pick request is a request for the React Native Release Crew to **include a commit** into a specific React Native release. As the development of React Native happens on main, you can request for a specific commit or Pull Request to be included in one of the previous version of React Native. We accepts pick requests only for versions of React Native that are **currently supported**
 
 ### What versions of React Native are currently supported?
@@ -16,28 +17,26 @@ Please refer to the official [Support Policy](https://github.com/reactwg/react-n
 React Native releases are run by a group of volunteers called the **Release Crew**.
 In those docs you can find clarification about the roles of the various members of the Release Crew:
 
-* [Roles & Responsibilities of Release Crew](./docs/roles-and-responsibilities.md)
-* [Release Escalation & Support Policy](./docs/support.md)
-* [FAQ](./docs/faq.md)
-* [Glossary](./docs/glossary.md)
+- [Roles & Responsibilities of Release Crew](./docs/roles-and-responsibilities.md)
+- [Release Escalation & Support Policy](./docs/support.md)
+- [FAQ](./docs/faq.md)
+- [Glossary](./docs/glossary.md)
 
 In those docs instead you can find step-by-step guides on how to run a React Native release
 
-* Guide: Running a Release
-  * [Version <= 0.73](./docs/guide-release-process-0.73.md)
-  * [Version == 0.74](./docs/guide-release-process-0.74.md)
-  * [Version >= 0.75](./docs/guide-release-process-0.75.md)
-* [Guide: Release Candidates](./docs/guide-release-candidate.md)
-    * [How to setup a new release project](./docs/guide-release-project-setup.md)
-    * [How to cut a release candidate](./docs/guide-release-candidate.md#cut-a-release-candidate)
-    * [Release Candidate patches](./docs/guide-release-candidate.md#release-patches-on-release-candidate)
-    * [Promote release candidate to stable](./docs/guide-release-candidate.md#promote-release-candidate-to-stable)
-* [Guide: Hermes Release](./docs/guide-hermes-release.md)
-* [Guide: Monorepo Packages Release](./docs/guide-publish-monorepo.md)
-* [Guide: Release Testing](./docs/guide-release-testing.md)
-* [Notable Call-outs / Gotchas](./docs/gotchas.md)
+- Guide: [Running a Release](./docs/guide-release-process.md)
+- [Guide: Release Candidates](./docs/guide-release-candidate.md)
+  - [How to setup a new release project](./docs/guide-release-project-setup.md)
+  - [How to cut a release candidate](./docs/guide-release-candidate.md#cut-a-release-candidate)
+  - [Release Candidate patches](./docs/guide-release-candidate.md#release-patches-on-release-candidate)
+  - [Promote release candidate to stable](./docs/guide-release-candidate.md#promote-release-candidate-to-stable)
+- [Guide: Hermes Release](./docs/guide-hermes-release.md)
+- [Guide: Release Testing](./docs/guide-release-testing.md)
+- [Notable Call-outs / Gotchas](./docs/gotchas.md)
 
 ### Reference Documentation
+
 These docs are not relevant for most releases but keeping them around in case of needing to patch an older release.
-* [Deprecated: Upgrade Helper](./docs/upgrade-helper.md)
-* [Deprecated: Release Dependencies](./docs/dependencies.md)
+
+- [Deprecated: Upgrade Helper](./docs/upgrade-helper.md)
+- [Deprecated: Release Dependencies](./docs/dependencies.md)

docs/faq.md

@@ -19,7 +19,7 @@ Everyone can open a pick request by [filing a GitHub issue via this link](https:
 
 Judgement call, but using these dimensions to evaluate:
 
-- Is it a fix for a regression introduced by the current release (for example, did it work in `v0.73.0` but it's broken in `v0.74.0`)?
+- Is it a fix for a regression introduced by the current release (for example, did it work in `v0.77.0` but it's broken in `v0.78.0`)?
 - Is it a fix for a critical developer workflow?
 
 ### What is release blocking?
@@ -31,7 +31,7 @@ Judgement call, but using these dimensions to evaluate:
 
 ### When will my fix make it into a release?
 
-We follow a release cycle that is not strictly monthly - you can read more [about it here](https://github.com/react-native-community/discussions-and-proposals/issues/17). When creating a new release, we cut a new branch from `main` (e.g. `0.74-stable`), with all the merged commits up to this point. After this initial cut, new commits on `main` will only be included on this release if they get manually cherry picked. Otherwise, they will be included in the next stable version (when a new cut from `main` will happen). This means that once a pull request is merged to the [core `react-native` repo](https://github.com/facebook/react-native), it may take one or two months for the changes to make it into a stable React Native release.
+We follow a release cycle that is not strictly monthly - you can read more [about it here](https://github.com/react-native-community/discussions-and-proposals/issues/17). When creating a new release, we cut a new branch from `main` (e.g. `0.77-stable`), with all the merged commits up to this point. After this initial cut, new commits on `main` will only be included on this release if they get manually cherry picked. Otherwise, they will be included in the next stable version (when a new cut from `main` will happen). This means that once a pull request is merged to the [core `react-native` repo](https://github.com/facebook/react-native), it may take one or two months for the changes to make it into a stable React Native release.
 
 ### How do I know if my fix/feature is in a certain release?
 

docs/guide-hermes-release.md

@@ -30,7 +30,7 @@ Push the picks to the remote branch.
 
 Head to the [Publish Tag workflow](https://github.com/facebook/hermes/actions/workflows/create-tag.yml) in the Hermes repo.
 
-Click the "Run Workflow" button. Run the workflow from `main`, input the React Native version you are releasing (ex. 0.73.5), and the SHA of the head of your Hermes release branch.
+Click the "Run Workflow" button. Run the workflow from `main`, input the React Native version you are releasing (ex. 0.78.1), and the SHA of the head of your Hermes release branch.
 
 <figure>
 <img src="../assets/hermes_publish_tag.png" width="400" />

docs/guide-publish-monorepo.md

@@ -100,16 +100,16 @@ In `fbsource` run
 ```bash
 js1 publish react-native 0.<your-release-candidate-minor+1>.0-main
 
-# ex. if you just released 0.75.0-rc.0, then
-js1 publish react-native 0.76.0-main
+# ex. if you just released 0.78.0-rc.0, then
+js1 publish react-native 0.79.0-main
 ```
 
-This will update all the relevant packages to `0.76.0-main`
+This will update all the relevant packages to `0.78.0-main`
 
 ## Release patches on release candidate
 You can follow the general release process for patches. The only thing to note is that your versioning scheme should be increasing the prerelease version.
 
-ex. 0.74.0-rc.1 -> 0.74.0-rc.2
+ex. 0.78.0-rc.1 -> 0.78.0-rc.2
 
 [See guide to release process](./guide-release-process-0.73.md)