DOCS Tracking releases

docs/en/05_Contributing/00_Issues_and_Bugs.md

@@ -63,7 +63,7 @@ read our guide on [how to write secure code](/developer_guides/security/secure_c
 * [forum.silverstripe.org](http://forum.silverstripe.org): Forums on silverstripe.org
 * [All issues across modules](https://www.silverstripe.org/community/contributing-to-silverstripe/github-all-core-issues)
 
-## Identifying issues and pull request relevant to your own project
+## Identifying issues and pull request relevant to your own project {#identifying-issues}
 
 Our [issue browser](https://silverstripe-github-issues.now.sh/) can be helpful to identify known issues and pending pull requests in
 [supported modules](https://www.silverstripe.org/software/addons/silverstripe-commercially-supported-module-list/).

docs/en/05_Contributing/04_Release_Process.md

@@ -29,9 +29,19 @@ They are prioritised by the core team as tickets on
 github.com. In addition, we collect community feedback as [feature ideas](https://forum.silverstripe.org/c/feature-ideas) on the forum.
 Any feature ideas we're planning to implement will be flagged there.
 
+## Keeping Track
+
 Release dates are usually not published prior to the release, but you can get a good idea of the release status by
 reviewing the release milestone on github.com. Releases will be
 announced on the ["releases" forum category](https://forum.silverstripe.org/c/releases).
+Significant releases will also be published via the [silverstripe.org blog](https://silverstripe.org/blog).
+
+You can also keep track of new releases through the CMS UI
+by installing the [maintenance module](https://github.com/bringyourownideas/silverstripe-maintenance),
+or using the [composer outdated](https://getcomposer.org/doc/03-cli.md#outdated) command in your project.
+
+Additionally, you can [keep track of issues](issues_and_bugs#identifying-issues) (both open and closed)
+across all modules involved in a recipe release.
 
 ## Release numbering {#release-numbering}