Skip to content

Commit 3964e71

Browse files
authored
Merge pull request #17466 from tacaswell/doc_milestone_implications
DOC: clarify that milestones are intentions not approvals
2 parents 0edefcd + 22d406a commit 3964e71

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

doc/devel/coding_guide.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,9 @@ Milestones
139139

140140
If multiple rules apply, choose the first matching from the above list.
141141

142+
Setting a milestone does not imply or guarantee that a PR will be merged for that
143+
release, but if it were to be merged what release it would be in.
144+
142145
All of these PRs should target the master branch. The milestone tag triggers
143146
an :ref:`automatic backport <automated-backports>` for milestones which have
144147
a corresponding branch.

0 commit comments

Comments
 (0)