- At the AGM we formed an ad-hoc documentation working group.
- One of our ideas was that we should have a last reviewed date for
documentation, so that we can periodically implement a review
mechanism (GitHub Actions posts to Slack for a regular documentation
outdatedness check?) to track how old docs are and ensure they're
still relevant.
- This is a first step towards that goal, by adding a `last_review_date`
to the metadata of all docs with a date of earlier than Homebrew's
inception because everything needs reviewing so that we start from a
good base!
- Note that Homebrew/homebrew-core CI jobs should complete successfully
before creating a release
- No code changes only required for 4 hours, 24 hours is a bit
excessive/unrealistic
- Note that commented `odeprecated` code should be uncommented
- TinyLetter emails are no longer required (MailChimp does so
automatically from the RSS feed)
- Note that `brew release` will output the major/minor blog post content
(after #10499 is merged) instead of referencing the now-deprecated
`brew release-notes`
- Note why you should not create a release on older `master` commits and
provide an alternate process to handle this case
- Various style tweaks
- Fix Markdown format
- Note Linux in the mission statement
- Update the maintainer guidelines based on current state
- Loosen the new maintainer expectations
- Clarify what things the PLC should be added to
- Add documentation for making a new Homebrew release
