From 1837c19833760e926a6daddc1616430d92e1dec2 Mon Sep 17 00:00:00 2001 From: Garion Herman Date: Fri, 9 Oct 2020 16:46:30 +1300 Subject: [PATCH] DOC Add note about creating provisional changelogs following minor releases --- .../05_Contributing/05_Making_A_SilverStripe_Core_Release.md | 3 +++ 1 file changed, 3 insertions(+) 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 b5579a0af..4a819d9c5 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 @@ -524,6 +524,9 @@ will need to be regularly updated. * 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. +* If you released a minor, raise a PR to add a provisional changelog for the next minor release based on the + [template](https://github.com/silverstripe/silverstripe-installer/blob/4/.cow/changelog.md.twig). This allows + contributors to start adding release notes for changes in the next minor prior to its release. ## See also