Skip to content

Policy for removal of old .. versionadded|.. versionchanged ? #108514

@Carreau

Description

@Carreau

A large number of .. versionadded, and .. versionchanged directive are from long-unmaintained version of Python, from a rough search through the codebase/docs (excluding whatsnew), of everything 3.5 and before:

   4 .. versionchanged:: 3.0
  33 .. versionchanged:: 3.1
  55 .. versionadded:: 3.1
 143 .. versionchanged:: 3.2
 152 .. versionadded:: 3.5
 159 .. versionchanged:: 3.4
 182 .. versionadded:: 3.4
 192 .. versionchanged:: 3.5
 209 .. versionchanged:: 3.3
 219 .. versionadded:: 3.2
 295 .. versionadded:: 3.3

I think that at some point it might be useful to remove those, and write the documentation as if what was changed/added has always be present.

Is there any policy as to when those can/should be removed/rephrased ?

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation in the Doc dirtype-featureA feature request or enhancement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions