Document security processes and releases

[annebdh]

There needs to be clear guidance for ROOST project users on how to stay informed of security releases (eg off-cadence security patch releases). For transparency, there should also be more information about ROOST's vulnerability response processes. Both of these are org-wide processes, but users will be looking for the information at the project level.

Proposal:

• Create a "Release cadence" section in both the Osprey and Coop documentation READMEs
• Create a "security-process" folder in /community. In README, explain off-cadence security releases, ROOST vuln response process, and how to stay up to date.
• In both project /docs/ READMEs:
  • State that both projects use semantic versioning, with very light explanation Document versioning styling #69
  • Link to roadmap
  • Explain that security releases may come off cycle, point to security-announce@roost.tools list as place for updates (in addition to GitHub Advisories) SECURITY.md: Add information about security updates .github#11
  • Link to "/community/security-process" for more info SECURITY.md: Add information about security updates .github#11

[cassidyjames]

Each of the bullet points above has been opened as its own issue or PR on our projects; as such, I think we can consider this issue closed.