closes #8824 Changelog rewording for 7.0

[ericluoliu]

No description provided.

[The-Compiler]

Great work, thanks! Just a couple of small remaining changes, as well as some remaining questions to other maintainers/contributors about things I'm not sure about.

As for dropping #8411, you'll need to remove the changelog/8411.trivial.rst file entirely (e.g. via git rm). We also agreed to move #8503 from internal to bugfix, which you can do by renaming 8503.trivial.rst to 8503.bugfix.rst (e.g. via git mv).

[The-Compiler]

This should probably be split off to a separate .deprecation.rst file? Or perhaps the whole thing should go under deprecations rather than improvements? @Zac-HD @olgarithms what do you think?

[Zac-HD]

Hmm. I think it probably makes most sense to move this entirely to a .deprecation.rst file, with a message like

:func:`pytest.warns(None) <pytest.warns>` is now deprecated because many people used
it to mean "this code does not emit warnings", but it actually had the effect of 
checking that the code emits at least one warning of any type - like ``pytest.warns()``
or ``pytest.warns(Warning)``.

[olgarithms]

Happy with this decision too!

[Zac-HD]

Suggested change

	Fixed issue where :meth:`unittest.TestCase.setUpClass` is not called when a test has `/` in its name since pytest 6.2.0.
	Fixed issue where :meth:`unittest.TestCase.setUpClass` is not called when a test has ``/`` in its name since pytest 6.2.0.

[nicoddemus]

Btw, no need to worry about ` vs `` because we configure the docs so they are equivalent:

pytest/doc/en/conf.py

Lines 102 to 103 in 5016375

	# The reST default role (used for this markup: `text`) to use for all documents.
	default_role = "literal"

[The-Compiler]

IMHO we should still be consistent though - right now we use an odd mix of both...

[nicoddemus]

Agree, just mentioning that to clarify that is not necessary to go hunting for those, unless inclined to spend time on it for consistency reasons, because otherwise the end result is the same.

[Zac-HD]

Hmm. I think it probably makes most sense to move this entirely to a .deprecation.rst file, with a message like

:func:`pytest.warns(None) <pytest.warns>` is now deprecated because many people used
it to mean "this code does not emit warnings", but it actually had the effect of 
checking that the code emits at least one warning of any type - like ``pytest.warns()``
or ``pytest.warns(Warning)``.

[The-Compiler]

One issue left from a quick look, afterwards I think this should be ready!

[The-Compiler]

Suggested change

	Defining a custom pytest node type which is both an :class:`pytest.Item <Item>` and a :class:pytest.Collector <Collector>` now issues a warning.
	Defining a custom pytest node type which is both an :class:`pytest.Item <Item>` and a :class:`pytest.Collector <Collector>` now issues a warning.

Last one hopefully! 🙂

[The-Compiler]

Looks great now - thanks a lot @ericluoliu, one step closer to 7.0 again! 🎉