Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document the process for deprecating an API in React #10057

Closed
4 tasks
flarnie opened this issue Jun 27, 2017 · 2 comments
Closed
4 tasks

Document the process for deprecating an API in React #10057

flarnie opened this issue Jun 27, 2017 · 2 comments
Assignees
@flarnie

Comments

@flarnie
Copy link
Contributor

flarnie commented Jun 27, 2017

Split out from #9398

  • what is the process for making that decision?
  • how do we communicate it before and during the release?
  • how do we support folks updating their syntax?
  • what should be included in a deprecation warning?
@flarnie flarnie self-assigned this Jun 27, 2017
@flarnie flarnie mentioned this issue Jun 27, 2017
Closed
49 tasks
@gaearon
Copy link
Collaborator

gaearon commented Oct 4, 2017 •
edited

Do we plan to do it? The current ad hoc process works. Who will read this and where?
If you don't feel strongly we can close it and revisit next time we deprecate something.

@flarnie
Copy link
Contributor Author

flarnie commented Oct 5, 2017

It was something that commenters had flagged as confusing on one of our release/checklist items, but since joining the team I observed that we have an "ad hoc" process that works, and it isn't something that seems useful to document. Let's close this for now - thanks!

@flarnie flarnie closed this as completed Oct 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flarnie flarnie

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gaearon @flarnie