@@ -12,9 +12,9 @@ Pull request checklist
12
12
Branch selection
13
13
----------------
14
14
15
- In general target the master branch for all new features and
16
- bug-fixes. PRs may target maintenance or doc branches on
17
- a case-by-case basis.
15
+ In general target the master branch for all new features and bug-fixes.
16
+ Pull requests (* PRs *) may target maintenance or doc branches on a case-by-case
17
+ basis.
18
18
19
19
20
20
Documentation
@@ -47,6 +47,19 @@ PR Review guidelines
47
47
* If you have commit rights, then you are trusted to use them. Please
48
48
help review and merge PRs!
49
49
50
+ * If you have the rights to set labels, tag the PR with descriptive labels.
51
+ See the `list of labels <https://github.com/matplotlib/matplotlib/labels >`__.
52
+
53
+ * Set the milestone to
54
+
55
+ * the next point-release for new features; e.g. ``v3.X.0 ``
56
+
57
+ * the next bugfix release for bugfixes; e.g. ``v.3.X.Y ``
58
+
59
+ All PRs for features and bug fixes should target the master branch. The
60
+ milestone tag triggers an :ref: `automatical backport <automated-backports >`.
61
+ for milestones which have a corresponding branch.
62
+
50
63
* Documentation and examples may be merged by the first reviewer. Use
51
64
the threshold "is this better than it was?" as the review criteria.
52
65
@@ -138,6 +151,8 @@ The only changes to be backported to 2.2.N-doc are changes to
138
151
``doc ``, ``examples ``, or ``tutorials ``. Any changes to
139
152
``lib `` or ``src `` should not be backported to this branch.
140
153
154
+ .. _automated-backports :
155
+
141
156
Automated backports
142
157
-------------------
143
158
0 commit comments