From a21bd9eff85490dccbf26cd7ba95e14af95ee9cd Mon Sep 17 00:00:00 2001 From: Aaron Carlino Date: Wed, 12 Jun 2019 10:57:09 +1200 Subject: [PATCH] MINOR: Ensure minor releases follow security release steps --- .../en/05_Contributing/05_Making_A_SilverStripe_Core_Release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/05_Contributing/05_Making_A_SilverStripe_Core_Release.md b/docs/en/05_Contributing/05_Making_A_SilverStripe_Core_Release.md index afbff7a02..6d8756ef5 100644 --- a/docs/en/05_Contributing/05_Making_A_SilverStripe_Core_Release.md +++ b/docs/en/05_Contributing/05_Making_A_SilverStripe_Core_Release.md @@ -479,7 +479,7 @@ will need to be regularly updated. * Update the [Slack](https://www.silverstripe.org/community/slack-signup/) topic to include the new release version. * For major or minor releases: Work with SilverStripe marketing to get a blog post out. They might choose to announce the release on social media as well. - +* If the minor or major release includes security fixes, follow the publication instructions in the [Security Release Process](#security-release-process) section. ## See also