diff --git a/website/contributing/_markdown-GH-release-notes-prerelease.mdx b/website/contributing/_markdown-GH-release-notes-prerelease.mdx new file mode 100644 index 00000000000..9e8501b2447 --- /dev/null +++ b/website/contributing/_markdown-GH-release-notes-prerelease.mdx @@ -0,0 +1,38 @@ +```markdown +- + +--- + +To test it, run: + + + +npx react-native init RN069RC0 --version 0.69.0-rc.0 + +--- + +- You can participate in the conversation on the status of this release in the [working group](https://github.com/reactwg/react-native-releases/discussions). + +- To help you upgrade to this version, you can use the [upgrade helper](https://react-native-community.github.io/upgrade-helper/) ⚛️ + +- See changes from this release in the [changelog PR](https://github.com/facebook/react-native/labels/%F0%9F%93%9D%20Changelog) + +--- + +### Help us testing 🧪 + + + +Let us know how it went by posting a comment in the [working group discussion](https://github.com/reactwg/react-native-releases/discussions)! Please specify with system you tried it on (ex. macos, windows). + +**Bonus points:** It would be even better if you could swap things around: instead of using a fresh new app, use a more complex one - or use a different library that is already leveraging the new architecture! +``` + +
+ Creating a GitHub Release +
Creating a GitHub Release.
+
diff --git a/website/contributing/_markdown-road-to-release-template.mdx b/website/contributing/_markdown-road-to-release-template.mdx new file mode 100644 index 00000000000..7bc928e6e48 --- /dev/null +++ b/website/contributing/_markdown-road-to-release-template.mdx @@ -0,0 +1,78 @@ +```markdown + + +The branch cut has happened. + +## Notice + + + +- [Current release candidate: 0.69.0-rc.0][current-release] +- Have an issue with current release candidate? [File an issue][issue-form] and we will triage. +- Have a pick request for this release? Does it fall under our [pick request qualifications][release-faq]? If so please create a PR against the release branch and comment with the PR link +- If you are release testing, copy and fill a [test checklist](/contributing/release-testing#test-checklist). + +#### Highlighted Changes in this release + + + +- Checkout this [Changelog PR][changelog-pr] + +## [Release Process][release-processes] + +#### Checklist + +- [ ] [Changelog PR][changelog-pr] +- [ ] Start a Google doc of blog post for release ([start from this skeleton](https://docs.google.com/document/d/1MP6AT-SX_qBrngOKRDbDoUIc_U2qhWq5L4dqgkLkd5Y/edit?usp=sharing)) and invite contributors of release highlights to expand +- [ ] Follow up on [release dependencies][release-dependencies] + > When ready to publish stable +- [ ] Ship changelog +- [ ] Ship blog post +- [ ] Prepare typescript PR (see https://github.com/DefinitelyTyped/DefinitelyTyped/pull/60929) +- [ ] Make PR to `react-native-website` with the new version cut ([see docs](https://github.com/facebook/react-native-website#cutting-a-new-version)) + +#### Retrospective Topics + + + +- + +## Release Status + +### Tracking 0.69.0-rc.1 + +#### Blocking issues for releasing 0.69.0-rc.1 + +- + +#### Picks for 0.69.0-rc.1 + +- + + + +[changelog-pr]: https://github.com/facebook/react-native/labels/%F0%9F%93%9D%20Changelog +[current-release]: https://github.com/facebook/react-native/releases +[changelog-wiki]: https://reactnative.dev/contributing/changelogs-in-pull-requests +[release-dependencies]: https://reactnative.dev/contributing/release-dependencies +[release-faq]: https://reactnative.dev/contributing/release-faq +[issue-form]: https://github.com/facebook/react-native/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Cpre-release&template=release_blocker_form.yml +[releases]: https://github.com/facebook/react-native/releases +[release-processes]: https://reactnative.dev/contributing/overview +[upgrade-helper]: https://reactnative.dev/contributing/updating-upgrade-helper +``` diff --git a/website/contributing/release-branch-cut-and-rc0.md b/website/contributing/release-branch-cut-and-rc0.md index b9d768ed10b..8fa43ad0795 100644 --- a/website/contributing/release-branch-cut-and-rc0.md +++ b/website/contributing/release-branch-cut-and-rc0.md @@ -4,6 +4,8 @@ title: Branch Cut & RC0 --- import AsyncTestingNote from './\_markdown-async-testing-note.mdx'; +import GHReleasesNotesPrerelease from './\_markdown-GH-release-notes-prerelease.mdx'; +import RoadToReleaseTemplate from './\_markdown-road-to-release-template.mdx'; :::info Documents in this section go over steps to run different types of React Native release updates. Its intended audience is those in [relevant release roles](./release-roles-responsibilites.md). @@ -96,36 +98,7 @@ Create a pull request of this change to `react-native` repo and add the `Changel - Create a [GitHub Release](https://github.com/facebook/react-native/releases) with this template and **check "Pre-Release" checkbox**. -```markdown - - -- - ---- - -To test it, run: - - - -npx react-native init RN069RC0 --version 0.69.0-rc.0 - ---- - -You can participate in the conversation on the status of this release in the [working group](https://github.com/reactwg/react-native-releases/discussions). - ---- - -To help you upgrade to this version, you can use the [upgrade helper](https://react-native-community.github.io/upgrade-helper/) ⚛️ - ---- - -See changes from this release in the [changelog PR](https://github.com/facebook/react-native/labels/%F0%9F%93%9D%20Changelog) -``` - -
- Creating a GitHub Release -
Creating a GitHub Release.
-
+ ### 6. Upload prebuilt Hermes binary @@ -135,67 +108,7 @@ In the `publish_release` CI workflow, the `build_hermes_macos` step produces a ` Create a "Road to " discussion post in the [`react-native-releases`](https://github.com/reactwg/react-native-releases/discussions) working group: -```markdown - - - -The branch cut has happened. - -## Notice - - - -- [Current release candidate: 0.69.0-rc.0][current-release] -- Have an issue with current release candidate? [File an issue][issue-form] and we will triage. -- Have a pick request for this release? Does it fall under our [pick request qualifications][release-faq]? If so please create a PR against the release branch and comment with the PR link -- If you are release testing, copy and fill a [test checklist](/contributing/release-testing#test-checklist). - -#### Highlighted Changes in this release - - - -- Checkout this [Changelog PR][changelog-pr] - -## [Release Process][release-processes] - -#### Checklist - -- [ ] [Changelog PR][changelog-pr] -- [ ] Start a Google doc of blog post for release and invite contributors of release highlights to expand -- [ ] Follow up on [release dependencies][release-dependencies] - > When ready to publish stable -- [ ] Ship changelog -- [ ] Ship blog post -- [ ] Make PR to `react-native-website` with the new version cut ([see docs](https://github.com/facebook/react-native-website#cutting-a-new-version)) - -#### Retrospective Topics - - - -- - -## Release Status - -### Tracking 0.69.0-rc.1 - -#### Blocking issues for releasing 0.69.0-rc.1 - -- - -#### Picks for 0.69.0-rc.1 - -- - -[changelog-pr]: https://github.com/facebook/react-native/labels/%F0%9F%93%9D%20Changelog -[current-release]: https://github.com/facebook/react-native/releases -[changelog-wiki]: https://reactnative.dev/contributing/changelogs-in-pull-requests -[release-dependencies]: https://reactnative.dev/contributing/release-dependencies -[release-faq]: https://reactnative.dev/contributing/release-faq -[issue-form]: https://github.com/facebook/react-native/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Cpre-release&template=release_blocker_form.yml -[releases]: https://github.com/facebook/react-native/releases -[release-processes]: https://reactnative.dev/contributing/overview -[upgrade-helper]: https://reactnative.dev/contributing/updating-upgrade-helper -``` + After creating it, make sure to link it in the relevant GitHub Release you created above, and to pin it in the discussion repo. diff --git a/website/contributing/release-candidate-patch.md b/website/contributing/release-candidate-patch.md index 1de7e2195ae..450f9995d3a 100644 --- a/website/contributing/release-candidate-patch.md +++ b/website/contributing/release-candidate-patch.md @@ -4,6 +4,7 @@ title: RC Patches --- import AsyncTestingNote from './\_markdown-async-testing-note.mdx'; +import GHReleasesNotesPrerelease from './\_markdown-GH-release-notes-prerelease.mdx'; :::info Documents in this section go over steps to run different types of React Native release updates. Its intended audience is those in [relevant release roles](./release-roles-responsibilites.md). @@ -63,11 +64,17 @@ git push latest: 0.(y-1).1 next: 0.y.0-rc.x nightly: 0.0.0-f617e022c ``` -### 5. Update the relevant discussion post with the latest RC +### 5. Create a GitHub Release + +- Create a [GitHub Release](https://github.com/facebook/react-native/releases) with this template and **check "Pre-Release" checkbox**. + + + +### 6. Update the relevant discussion post with the latest RC Go back to the "road to 0.XX.0" [discussion](https://github.com/reactwg/react-native-releases/discussions) and update the "Current release candidate" line with the new version you published. -### 6. Broadcast that release candidate is out +### 7. Broadcast that release candidate is out Once all the steps above have been completed, it's time to signal to the community that the new RC is available for testing! Do so in the following channels: