Skip to content

NEP: update status fields of many NEPs#25920

Merged
charris merged 2 commits intonumpy:mainfrom
rgommers:neps-update-statuses
Mar 4, 2024
Merged

NEP: update status fields of many NEPs#25920
charris merged 2 commits intonumpy:mainfrom
rgommers:neps-update-statuses

Conversation

@rgommers
Copy link
Member

@rgommers rgommers commented Mar 3, 2024

The first commit marks NEPs 30, 31, 37, and 47 as superseded (by NEP 56), and NEP 56 as accepted, since it's done and 99.x% implemented. The NEP doc build tooling needed a small update to allow the metadata in one NEP to list several others in :Replaces:.

The second commit updates the status of active process NEPs, marks NEP 21 as deferred, and NEP 38 as final:

  • We marked process NEPs as Accepted/Final so far, but the intent of policy/process NEPs that still apply and can be updated when we update our development processes or project policies is that they are marked as Active, so they show up under "Meta-NEPs".
  • NEP 21 (oindex/vindex) is still considered perhaps a good idea, but hasn't been touched in many years (it's from 2015), so mark it as Deferred.
  • NEP 38 (SIMD) was finished several years ago, so mark it as Final.

Overall this should give a better picture of the current state of development and thinking. There are only four NEPs left under Draft, and NEP 50 (type promotion) and NEP (C API changes for 2.0) should be moving to Accepted soon as well. I chose not to touch those, since for NEP 50 there is still a fair bit in flight, and NEP 53 seems to need some updates for what was actually implemented (at a high level, forexample a compat header rather than a separate library).

I'll send an email to the mailing list about this PR.

rgommers added 2 commits March 3, 2024 18:56
Mark 56 as Accepted, and the other ones as superseded.

The NEP doc build tooling needed a small update to allow the metadata in
one NEP to list several others in `:Replaces:`.

[skip azp] [skip actions] [skip cirrus]
We marked process NEPs as Accepted/Final so far, but the intent of
policy/process NEPs that still apply and can be updated when we
update our development processes or project policies is that they
are marked as Active, so they show up under "Meta-NEPs".

NEP 21 is still considered perhaps a good idea, but hasn't been
touched in many years (it's from 2015), so mark it as Deferred.

NEP 38 was finished several years ago, so mark it as Final.

[skip actions] [skip azp] [skip cirrus]
@mattip
Copy link
Member

mattip commented Mar 4, 2024

LGTM.

It might be nice, maybe in a future PR, to make the "Replaced by: " text a :ref: link to the other NEP.

@rgommers
Copy link
Member Author

rgommers commented Mar 4, 2024

It might be nice, maybe in a future PR, to make the "Replaced by: " text a :ref: link to the other NEP.

Good idea. I'll open an issue for that. May be nice for a new contributor; it's not urgent.

@charris charris merged commit 8ed37a6 into numpy:main Mar 4, 2024
@charris
Copy link
Member

charris commented Mar 4, 2024

Thanks Ralf.

@rgommers rgommers deleted the neps-update-statuses branch March 4, 2024 15:21
@rgommers rgommers added this to the 2.0.0 release milestone Mar 4, 2024
@stefanv
Copy link
Contributor

stefanv commented Mar 5, 2024

Thanks for doing the review 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants