Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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.

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

Already on GitHub?Sign in to your account

Merged
willingc merged 13 commits intopython:masterfromwillingc:triage-updates
Mar 14, 2018
Merged
Changes from1 commit
Commits
Show all changes
13 commits
Select commitHold shift + click to select a range
21dabaa
Update triage page to change type section to table
willingcMar 11, 2018
b0697b6
Convert Stage to a table
willingcMar 11, 2018
1d2b651
Convert tables and add initial checklist
willingcMar 11, 2018
bbf39d8
Convert comment section to table
willingcMar 12, 2018
a96ed8a
Fix typos
willingcMar 12, 2018
bd16b7a
Add content about sections in an issue and to checklist
willingcMar 12, 2018
42f74ec
Correct wonky indentation
willingcMar 12, 2018
efec7c8
Update intro as bpo links to this section as its documentation
willingcMar 12, 2018
77afdbe
Edits per @csabella @brettcannon review
willingcMar 13, 2018
fc63ad9
Clarify later and postponed per mailing list post
willingcMar 13, 2018
577c560
Add pull request as suggested by @ncoghlan
willingcMar 14, 2018
afacd4e
Fix typos
willingcMar 14, 2018
0a23131
Edits per @ncoghlan review
willingcMar 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
PrevPrevious commit
NextNext commit
Add pull request as suggested by@ncoghlan
  • Loading branch information
@willingc
willingc committedMar 14, 2018
commit577c560c2df20af198e135de56ca683e5d7e66c4
26 changes: 14 additions & 12 deletionstriaging.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -29,7 +29,8 @@ A brief description of the issue. Review whether the title is too generic or
specifies an incorrect term or library.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I mentioned this in my other comment, but mentioning it here too. This may need to be a new issue for further discussion. I think it would be helpful for the title to begin with the module that the issue is for. A large portion of the tickets have this now, but not all of them. It makes search (and sorting) easier to find tickets related to a module.

Copy link
CollaboratorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Let's recommend that folks do as you suggest. Do you have a format that has worked well?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thanks for asking! :-) Well, for IDLE, we useIDLE: and I think that let's everyone know they can skip it. :-) Seriously though, if you go into the bug tracker and then search, then click 'Sort on' next to title, you'll see (with sort descending), that thezlib andzip modules come up first. That's really just the format I'd suggest, putting the module first instead of somewhere else in the title. I don't think a colon after it is necessary, unless it reads better. I've downloaded all the bugs using the .csv download and realized this could make it a lot easier for people to find related tickets. The old 'I think there's a ticket for this, but I can't find it' becomes easier when you can narrow the search. :-) It also gives a sense for the modules that may be neglected (for example, argparse has a ton of open tickets).

Copy link
CollaboratorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@csabella Added below and in the checklist.


Adding a prefix at the start of the title to indicate the module, such as
IDLE, DOC, or ASYNCIO, is optional, but can be helpful to others.
IDLE, doc, or asycio, for example, are optional, but can be helpful to
others.

Type
''''
Expand DownExpand Up@@ -81,20 +82,20 @@ will be needed.
| | bug reporter should post a script, instructions, or |
| | example to help someone test or reproduce the issue. |
+---------------+----------------------------------------------------------+
| needs patch | A patch is needed to solve the problem (i.e. fixing the |
| | bug or adding the requested improvement). |
| needs patch | A patch or pull request is needed to solve the problem |
| | (i.e. fixing the bug or adding the requested |
| | improvement). |
+---------------+----------------------------------------------------------+
| patch review | A patch exists, but it needs reviewing or is in the |
| | process of being reviewed. This can be done by any |
| | triager as well as a core developer. |
| patch review | A patch or pull request exists, but it needs review. |
| | Any triager or core developer may do the review. |
+---------------+----------------------------------------------------------+
| commit review | A triager performed a patch review and it looks good. |
| | This signals to core developers the patchis ready for a |
| | quick once-over to make sure nothing was overlooked |
| | before committingthe patch. |
| | This signals to core developers the patchor pull |
| |request needs aquick once-over to make sure nothing was |
| |overlookedbefore committingit. |
+---------------+----------------------------------------------------------+
| resolved | The issue is considered closed and addressed (i.e. patch |
| |committedorexpected behavior and not a bug). |
| | orpull request committed; expected behavior). |
+---------------+----------------------------------------------------------+

Components
Expand DownExpand Up@@ -214,9 +215,10 @@ Various informational flags about the issue. Multiple values are possible.
+---------------+------------------------------------------------------------+
| gsoc | The issue would fit as, or is related to, a GSoC_ project. |
+---------------+------------------------------------------------------------+
| needs review | The patch attached to the issue is in need of a review. |
| needs review | The patch or pull request attached to the issue is in need |
| | of a review. |
+---------------+------------------------------------------------------------+
| patch | There is a patch attached to the issue. |
| patch | There is a patchor pull requestattached to the issue. |
+---------------+------------------------------------------------------------+
| 3.3regression | The issue is a regression in 3.3. |
+---------------+------------------------------------------------------------+
Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp