> Descriptive text looks fine. Alerts about updating the corresponding user > guide passages may be helpful, but one wonders if they're truly necessary. > Shouldn't developers _always_ check behavioral changes against the > documentation? Never mind, silly question :)
I agree in an ideal world this shouldn't happen, but the truth is it already did (which prompted part of this PR). Someone saw new dependencies were added which caused a test to fail, so they fixed the test but the documentation remained stale. Any hints we can give to someone who is fixing a broken test to also fix the documentation doesn't hurt ;P. [ Full content available at: https://github.com/apache/geode/pull/3886 ] This message was relayed via gitbox.apache.org for [email protected]
