Skip to content

MAINT: NEP process updates - #10703

Merged
charris merged 2 commits into
numpy:masterfrom
njsmith:nep-nep-nep
Mar 8, 2018
Merged

charris merged 2 commits into
numpy:masterfrom
njsmith:nep-nep-nep

Conversation

@njsmith

@njsmith njsmith commented Mar 8, 2018

Copy link
Copy Markdown
Member
  • Write down a formal procedure for declaring a NEP "accepted"

  • Assign numbers to all existing NEPs

@njsmith

njsmith commented Mar 8, 2018

Copy link
Copy Markdown
Member Author

CC @jarrodmillman @stefanv

@eric-wieser

Copy link
Copy Markdown
Member

Do we want to reserve some early numbers to become things like HOW_TO_DOCUMENT and other instructional documents?

So maybe start numbering at 100?

@njsmith

njsmith commented Mar 8, 2018

Copy link
Copy Markdown
Member Author

I just figured we'd allocate those numbers as they come up? I'm not sure which ones are "special enough" to get "special numbers", and I'm not sure that NEP 5 or whatever is that much more memorable than NEP 25 anyway...

@charris

charris commented Mar 8, 2018

Copy link
Copy Markdown
Member

I don't have a problem with the numbering, it is kind of arbitrary anyway.

@charris
charris self-requested a review March 8, 2018 18:07
@charris

charris commented Mar 8, 2018

Copy link
Copy Markdown
Member

Let's get this in so @njsmith can add entries in his NEP PRs. Thanks Nathaniel.

@charris
charris merged commit a3c05b1 into numpy:master Mar 8, 2018
@stefanv

stefanv commented Mar 8, 2018

Copy link
Copy Markdown
Contributor

Looks good, thanks!

@njsmith
njsmith deleted the nep-nep-nep branch March 9, 2018 00:45
@charris charris changed the title NEP process updates MAINT: NEP process updates Jun 16, 2018
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