docs: add major release strategy, fix typos #5551
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Issue Reference
In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.
JoshuaKGoldberg
left a comment
JoshuaKGoldberg
left a comment
There was a problem hiding this comment.
Looking great! You clearly did a bunch of research and thought this through. It shows. 🙂
| For large releases, we recommend betas, then release candidates (RCs), then a full release. | ||
| Betas are when most features are available, but more will likely be added before full release. | ||
| RCs are almost ready for release, but would benefit from user testing before a full release. | ||
| Betas and/or RCs can be skipped, neither of those phases are ever necessary. |
There was a problem hiding this comment.
I don't think this will ever be the case for large releases anytime soon. We've got a lot of bigger changes lined up that will eventually get released as larger changes.
| Betas and/or RCs can be skipped, neither of those phases are ever necessary. |
PR Checklist
status: accepting prsOverview
Both high-level guidance and low-level implementation details. Couldn't find a good other spot for implementation details, might open a separate issue for that if I get bored :D