summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAndré Arko <andre@arko.net>2020-01-25 14:35:59 -0800
committerGitHub <noreply@github.com>2020-01-25 14:35:59 -0800
commitedd70ffc1ceb2c6d5ea5f171827ba767c4ca813e (patch)
treeaf7c8f971f03f469234dcfcfb4e6bcf3b6e321fe /doc
parent713b3c82daf177631bd52ad42cd0b7cfd642bb22 (diff)
downloadbundler-edd70ffc1ceb2c6d5ea5f171827ba767c4ca813e.tar.gz
Clarify doc updates for minors
Diffstat (limited to 'doc')
-rw-r--r--doc/POLICIES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/POLICIES.md b/doc/POLICIES.md
index e4a9243374..39d8747210 100644
--- a/doc/POLICIES.md
+++ b/doc/POLICIES.md
@@ -25,7 +25,7 @@ These policies are not a guarantee that any particular fix will be backported. I
Bugfix releases should generally be cut as soon as possible. A bugfix release for a single PR is totally okay.
-Minor/feature releases can be cut anytime at least one new feature is ready, but don't have to be. Minor version releases should include an update to the documentation website.
+Minor/feature releases can be cut anytime at least one new feature is ready, but don't have to be. Minor version releases must also include any needed updates to the documentation website, plus a "What's new" page summarizing what was added.
Major version releases should be cut no more than once per year, and must include a new section of the website with documentation for that major version.