Adjust dockerng/dockerio docstrings #27332
Merged
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
This adds a similar documentation section to the top of the state module to match the one in the execution module. It also updates the expected release date of the Carbon release to reflect the new release cadence.
cro
added a commit
that referenced
this pull request
Sep 24, 2015
Adjust dockerng/dockerio docstrings
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 adds a similar documentation section to the top of the state module to
match the one in the execution module. It also updates the expected release
date of the Carbon release to reflect the new release cadence.
It also adds a deprecation notice to the dockerio state module, and corrects
the name of the dockerng module in the deprecation notice from the dockerio
execution module docstring. It was changed from docker-ng to dockerng early on
and this change was never reflected in the deprecation notice.