Proposal for JEP deprecations #19
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
For context, the JEP process was modeled after how other languages/standards propose changes. Most of these processes just use a single integer. The numbers in the JEPs don't really mean anything, they're just an identifier to refer to a feature. I'm not even picky if we skip numbers (I'll probably just end up using the PR numbers). The RFC process has an For now, if you'd like to update the PR with the typo updates, I'd be happy to merge those. |
jamesls
added a commit
that referenced
this pull request
Mar 31, 2023
Pulled in updates from #19: * Fix typos * Add note about JEP number assignment Also: * Add link to rendered docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR proposes a numbering scheme for deprecation of existing JEPs.