Skip to content

Update triage page with tables #339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
willingc merged 13 commits into from
Mar 14, 2018
Merged

Update triage page with tables #339

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
21dabaa
Update triage page to change type section to table
willingc Mar 11, 2018
b0697b6
Convert Stage to a table
willingc Mar 11, 2018
1d2b651
Convert tables and add initial checklist
willingc Mar 11, 2018
bbf39d8
Convert comment section to table
willingc Mar 12, 2018
a96ed8a
Fix typos
willingc Mar 12, 2018
bd16b7a
Add content about sections in an issue and to checklist
willingc Mar 12, 2018
42f74ec
Correct wonky indentation
willingc Mar 12, 2018
efec7c8
Update intro as bpo links to this section as its documentation
willingc Mar 12, 2018
77afdbe
Edits per @csabella @brettcannon review
willingc Mar 13, 2018
fc63ad9
Clarify later and postponed per mailing list post
willingc Mar 13, 2018
577c560
Add pull request as suggested by @ncoghlan
willingc Mar 14, 2018
afacd4e
Fix typos
willingc Mar 14, 2018
0a23131
Edits per @ncoghlan review
willingc Mar 14, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Clarify later and postponed per mailing list post
  • Loading branch information
@willingc
willingc committed Mar 13, 2018
commit fc63ad975dfa81b2aa48acb7665a91d0ee9134d8
8 changes: 5 additions & 3 deletions triaging.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -278,7 +278,8 @@ Status
| | information to reproduce the bug reported. Requesting |
| | additional information and setting status to *pending* |
| | indicates that the issue should be closed if the necessary |
| | information in a timely manner (i.e. one month). |
| | information is not provided in a timely manner (i.e. one |
| | month). |
+---------------+------------------------------------------------------------+
| closed | The issue has been resolved (somehow). |
+---------------+------------------------------------------------------------+
Expand All @@ -298,15 +299,16 @@ with the "open" status.
+---------------+------------------------------------------------------------+
| fixed | A fix for the issue was committed. |
+---------------+------------------------------------------------------------+
| later | Issue is to be worked on at a later date. |
| later | Issue is to be worked on in a later release cycle. |
+---------------+------------------------------------------------------------+
| not a bug | For some reason the issue is invalid (e.g. the perceived |
| | problem is not a bug in Python). |
+---------------+------------------------------------------------------------+
| out of date | The issue has already been fixed, or the problem doesn't |
| | exist anymore for other reasons. |
+---------------+------------------------------------------------------------+
| postponed | Issue will not be worked on at the moment. |
| postponed | Issue will not be worked on at the moment but in a future |
| | minor release version. |
+---------------+------------------------------------------------------------+
| rejected | Issue was rejected (especially for feature requests). |
+---------------+------------------------------------------------------------+
Expand Down