Skip to content

docs: mention trying major version betas on plugins #9502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/maintenance/Releases.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,11 @@ In parallel to the general PR flow of the major version:

In parallel to the shared config changes work, make sure to test out the beta version on popular community projects willing to try it out.

1. Create a pinned issue offering to try out the new version's beta for consumers [example: [Try out v8 beta on various influential community repos](https://github.com/typescript-eslint/typescript-eslint/issues/9141)]
- Ask each community project if they'd be interested in trying out the new version, such as in their Discord or on their issue tracker.
1. Create a pinned issue offering to try out the new version's beta for end users (example: [Try out v8 beta on various influential community repos](https://github.com/typescript-eslint/typescript-eslint/issues/9141))
- Ask each community repo if they'd be interested in trying out the new version, such as in their Discord or on their issue tracker.
- Each community project that's indicated willingness to receive a PR should have one.
1. Create a pinned issue offering to try the new version's beta for downstream plugins (example: [Try out v8 beta on various influential plugins](https://github.com/typescript-eslint/typescript-eslint/issues/9501))
- These PRs can be sent without asking, as a friendly courtesy.
1. Once the proposed _Shared Config Changes_ are merged into the `v${major}` branch, send a draft PR to each project with the new beta version.

#### 1c. Post Community Testing Config Touchups
Expand Down
Loading