On the topic of issue triage, this is a service we could promote people to
use. But I guess it's a question if the problem is more rate of new issues
or old issues never getting closed.
Brianna
---------- Forwarded message ---------
From: CodeTriage <noreply(a)codetriage.com>
Date: Sun, 9 Sep 2018 at 16:38
Subject: [CodeTriage] Help triage pytest-dev/pytest
To: <brianna.laugher(a)gmail.com>
Hello pfctdayelise,
Repo added to CodeTriage!
Thank you for adding pytest-dev/pytest to CodeTriage. If you want to get
more people helping out with this repo, we suggest adding a badge to the
repo’s readme. Here is the markdown:
[](https://…
You can view an the badge on the CodeTriage page for pytest
<https://u307627.ct.sendgrid.net/wf/click?upn=MUrV-2BnW5j8SEy7InNvMchphxrykv…>
.
If pytest has a “contributing section” or docs on helping such as
contributing.md, it helps to put a sentence or two encouraging people to
subscribe to your repo:
You can triage issues which may include reproducing bug reports
or asking for vital information, such as version numbers or
reproduction instructions. If you would like to start triaging
issues, one easy way to get started is to [subscribe to pytest on
CodeTriage](https://codetriage.com/pytest-dev/pytest).
The more people you have subscribed to this repo on CodeTriage, the more
help it will get on this project. The more 👀’s the better.
------------------------------
You subscribed to pytest on CodeTriage!
You signed up to help triage GitHub issues on pytest-dev/pytest
<https://u307627.ct.sendgrid.net/wf/click?upn=E2E2DIkTqIajPU6hMNRcRHG-2Flbe4…>.
That’s pretty awesome.
What’s next? You’ll get issues sent to your inbox periodically like this
one:
*pytest-dev/pytest#2449* warnings: support for logging.captureWarnings
<https://u307627.ct.sendgrid.net/wf/click?upn=E2E2DIkTqIajPU6hMNRcRHG-2Flbe4…>
The rate at which we send emails backs off automatically when you get busy.
You can also set you prefered email rate in your user settings.
What do you do with an issue when it gets in your inbox? Try to triage it.
How To Triage?
First, carefully read over the issue, title, and description, if there are
any comments read over all the comments, carefully. If a member of this
repo is engaging actively there is no need to do anything, leaving a
comment in the issue would just add to the clutter.
If the issue hasn’t been updated in awhile, or if no one has commented
consider the issue, if it is a bug try to reproduce it. If it is a pull
request consider what an alternate implementation might look like. If there
is something you don’t understand about the issue and feel others will have
that same question please leave your question in the comments. Be as
descriptive as possible. Comments like “I don’t understand this” are not
helpful and counter productive. A better comment might be “Can you help me
understand a use case for this?”.
If you can reproduce the issue or you believe it is a good pull request,
add a comment and say why you think that is. Try to stay positive while
triaging issues, ask questions before you downvote something. If you do
decide to 👍 or 👎 on an issue, leave a comment as to why you feel that
way. Issues are for social coding, if you help someone make better issues,
you’re helping the community.
If the issue goes stale, leave a comment asking if it is still a problem.
If you get no response for a number of days, you can leave another comment
suggesting to the repo owner that they should close the issue.
Read more about Fixing Open Source Issues via Triage
<https://u307627.ct.sendgrid.net/wf/click?upn=gvZlbyjGw-2B4Vj3enF605apAySa8E…>
.
Goals of Triage
- Help share the weight of maintaining a project
- Minimize un-needed issues
- Prevent stale issues
- Encourage productive communication
- Teach good citizenship
- To become a better coder
Go forth and make the world a better place
Sincerely,
schneems
<https://u307627.ct.sendgrid.net/wf/click?upn=HwDhLwOSLCgrJQpXhIJyyTVZeHekFO…>
--
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
The pytest team is proud to announce the 3.8.0 release!
pytest is a mature Python testing tool with more than a 2000 tests
against itself, passing on many different interpreters and platforms.
This release introduces a refactoring of warnings generated by pytest
itself, making clearer when features are deprecated and when they are
planned for removal. Also fixes a number of long standing issues with
warnings capture.
Users are encouraged to take a look at the CHANGELOG:
https://docs.pytest.org/en/latest/changelog.html
For complete documentation, please visit:
https://docs.pytest.org/en/latest/
As usual, you can upgrade from pypi via:
pip install -U pytest
Thanks to all who contributed to this release, among them:
* Anthony Sottile
* Bruno Oliveira
* CrazyMerlyn
* Daniel Hahler
* Fabio Zadrozny
* Jeffrey Rackauckas
* Ronny Pfannschmidt
* Virgil Dupras
* dhirensr
* hoefling
* wim glenn
Happy testing,
The Pytest Development Team
](https://…](http://badge](https://codetriage.com/pytest-dev/pytest/badges/users.svg)](https://codetriage.com/pytest-dev/pytest)){kind=link}