René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Doc]: add sphinx versioning directives","articleBody":"### Documentation Link\r\n\r\n_No response_\r\n\r\n### Problem\r\n\r\nIt can be unclear which features were added when just by looking at the docs, and would be helpful if at at least major features (and whatever else folks think would be a good idea) could be flagged with a version added/changed/etc directive. \r\n\r\n### Suggested improvement\r\n\r\nIntroduce the [versioning directives](https://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html?highlight=versionadded#directive-versionadded)\r\n\r\nPer the call ([link](https://hackmd.io/49a-u44CTja02xQRaG88JA?both#other-comments)), a first step is to create a pr with some sample directives:\r\n- https://github.com/matplotlib/matplotlib/pull/24160\r\n\r\nAdditionally sort out guidance for adding directive (to which prs) and update PR guidelines accordingly :\r\n- https://github.com/matplotlib/matplotlib/pull/24161\r\n\r\nAs a first pass, my guess is anything that gets a what's new should get a version added, anything that gets an api change should get a versionchanged, and `deprecated` is already added as part of the decorator https://github.com/matplotlib/matplotlib/blob/862f85d37a0f0da270d93aa3a59157bb9f1553d3/lib/matplotlib/_api/deprecation.py#L210","author":{"url":"https://github.com/story645","@type":"Person","name":"story645"},"datePublished":"2022-07-28T20:58:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":14},"url":"https://github.com/23506/matplotlib/issues/23506"}