DOC: Set status of NEP 29 to 'superseded'

[Aloqeely]

Issue with current documentation:

In https://numpy.org/neps/nep-0029-deprecation_policy.html the status is set as 'final' but a note says that it's been superseded by SPEC 0

Idea or request for content:

Set the status to superseded

[mattip]

I think "superseded" is a bit strong. We have not really adopted the version deprecation policy suggested in SPEC 0 for NumPy itself. For other projects, we suggest they adopt SPEC 0 and not NEP 29, but that is more of a recommendation than a hard requirement.

[seberg]

Well, we never really adopted NEP 29 either I believe, which is why it is in the "informational" category :). Just like SPEC 0 it was always a recommendation and not a strict rule NumPy adhers to. It is definitely not superseded in the sense of the new one overruling anything (it wouldn't make sense, since it never defined our policy anyway :)).

I don't think it matters what it is categorized as, maybe the authors should just decide. I think it can just stay final, it isn't like it even can become incorrect from a NumPy policy perspective (although the yearly Python release schedule might make it fuzzy).