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.

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

Clarify that ReactPerf.getLastMeasurements() is now opaque #6405

Merged
merged 1 commit into from
Apr 4, 2016

Conversation

gaearon
Copy link
Collaborator

@gaearon gaearon commented Apr 4, 2016

This documents changes from #6286 and should be up on the website when 15 is released.

@jimfb
Copy link
Contributor

jimfb commented Apr 4, 2016

👍

@gaearon
Copy link
Collaborator Author

gaearon commented Apr 4, 2016

Should I merge it now, or wait for 15 to be released? How do we divide “needs merge to stable asap” from “needs merge to stable on next release”?

@jimfb
Copy link
Contributor

jimfb commented Apr 4, 2016

Merge now but do not mark as needing to be cherry-picked to stable.

@gaearon
Copy link
Collaborator Author

gaearon commented Apr 4, 2016

How do we remember to cherry-pick it later? Is this part of the stable release process?

@gaearon gaearon merged commit b0d1e16 into master Apr 4, 2016
@gaearon gaearon deleted the gaearon-patch-2 branch April 4, 2016 16:02
@jimfb
Copy link
Contributor

jimfb commented Apr 4, 2016

We never cherry-pick it. When the v15 branch is cut, it will be cut from master, so it will include this commit. The cherry-picking is only for backporting the documentation to the previous stable release.

@gaearon
Copy link
Collaborator Author

gaearon commented Apr 4, 2016

Ah, that makes total sense. Thanks!

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.

3 participants