@@ -44,6 +44,9 @@ reading.
44
44
Issue triage
45
45
------------
46
46
47
+ Triage is an important first step in addressing issues reported by the community, and even
48
+ partial contributions are a great way to help maintain pandas. Only remove the "Needs Triage"
49
+ tag once all of the steps below have been completed.
47
50
48
51
Here's a typical workflow for triaging a newly opened issue.
49
52
@@ -67,9 +70,9 @@ Here's a typical workflow for triaging a newly opened issue.
67
70
3. **Is this a duplicate issue? **
68
71
69
72
We have many open issues. If a new issue is clearly a duplicate, label the
70
- new issue as "Duplicate" assign the milestone "No Action", and close the issue
71
- with a link to the original issue. Make sure to still thank the reporter, and
72
- encourage them to chime in on the original issue, and perhaps try to fix it.
73
+ new issue as "Duplicate" and close the issue with a link to the original issue.
74
+ Make sure to still thank the reporter, and encourage them to chime in on the
75
+ original issue, and perhaps try to fix it.
73
76
74
77
If the new issue provides relevant information, such as a better or slightly
75
78
different example, add it to the original issue as a comment or an edit to
@@ -90,15 +93,20 @@ Here's a typical workflow for triaging a newly opened issue.
90
93
If a reproducible example is provided, but you see a simplification,
91
94
edit the original post with your simpler reproducible example.
92
95
96
+ Ensure the issue exists on the main branch and that it has the "Needs Triage" tag
97
+ until all steps have been completed. Add a comment to the issue once you have
98
+ verified it exists on the main branch, so others know it has been confirmed.
99
+
93
100
5. **Is this a clearly defined feature request? **
94
101
95
102
Generally, pandas prefers to discuss and design new features in issues, before
96
103
a pull request is made. Encourage the submitter to include a proposed API
97
104
for the new feature. Having them write a full docstring is a good way to
98
105
pin down specifics.
99
106
100
- We'll need a discussion from several pandas maintainers before deciding whether
101
- the proposal is in scope for pandas.
107
+ Tag new feature requests with "Needs Discussion", as we'll need a discussion
108
+ from several pandas maintainers before deciding whether the proposal is in
109
+ scope for pandas.
102
110
103
111
6. **Is this a usage question? **
104
112
@@ -117,10 +125,6 @@ Here's a typical workflow for triaging a newly opened issue.
117
125
If the issue is clearly defined and the fix seems relatively straightforward,
118
126
label the issue as "Good first issue".
119
127
120
- Typically, new issues will be assigned the "Contributions welcome" milestone,
121
- unless it's know that this issue should be addressed in a specific release (say
122
- because it's a large regression).
123
-
124
128
Once you have completed the above, make sure to remove the "needs triage" label.
125
129
126
130
.. _maintaining.regressions :
0 commit comments