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

document various reset strategies #7789

Closed
jlipps opened this issue Feb 1, 2017 · 1 comment
Closed

document various reset strategies #7789

jlipps opened this issue Feb 1, 2017 · 1 comment
Assignees
Labels
Documentation related to writing, reading, or generating documentation Enhancement feature

Comments

@jlipps
Copy link
Member

jlipps commented Feb 1, 2017

There's a lot of confusion at the moment about the three reset strategies (noReset, fullReset, and the default reset, which doesn't have a capability and internally is called fastReset). We should have a table in our documentation that describes that they each do, for each of our drivers, that we can point people to.

@jlipps jlipps added Documentation related to writing, reading, or generating documentation Enhancement feature labels Feb 1, 2017
@triager triager added the Needs Triage bugs which are not yet confirmed label Feb 1, 2017
@jlipps jlipps removed the Needs Triage bugs which are not yet confirmed label Feb 1, 2017
@jlipps jlipps added this to the T-1000 [Sprint 10] milestone Apr 10, 2017
@dpgraham dpgraham self-assigned this May 2, 2017
@lock
Copy link

lock bot commented Apr 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Apr 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation related to writing, reading, or generating documentation Enhancement feature
Projects
None yet
Development

No branches or pull requests

3 participants