Skip to content

Add information about watching changes (NFC) #8011

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

KangarooKoala
Copy link
Contributor

Related to wpilibsuite/frc-docs#3049.

Also updates the README.md table of contents.


Below are some ways to keep up-to-date on what changes are being made to the repository, in order from lowest effort to highest effort.

- **Read release notes and/or the yearlog changelog.** Every release contains a summary of the changes made since the last release. In addition, frc-docs contains a [yearly changelog](https://docs.wpilib.org/en/stable/docs/yearly-overview/yearly-changelog.html) summarizing the changes made since the previous season.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the first one should be rule book and team updates, for info about required versions and very high importance changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe? I feel like required versions doesn't really fit the goal of this section though (how to "keep up-to-date on what changes are being made to the repository"), and I wouldn't consider reading the team updates an effective recommendation for how to see the major changes because the team updates rarely mention anything about WPILib. It might be nice though to at least mention the team updates, since they are a pretty important resource for FRC overall.

So overall, not sure about if we should talk about the team updates. What do other people think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants