This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Clarify module dependency rule wording #4826
Merged
Conversation
This file contains hidden or 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
|
|
|
An admin must run tests on this PR before it can be merged. |
buskamuza
approved these changes
Jun 24, 2019
erikmarr
added
2.1.x
2.2.x
2.3.x
erikmarr
approved these changes
Jun 26, 2019
osrecio
approved these changes
Jun 27, 2019
|
Hi @scottsb, thank you for your contribution! |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Purpose of this pull request
This pull request (PR) clarifies the backwards compatibility rule about adding new dependencies between Magento modules. Previously I had trouble understanding what it was saying.
See for further context:
https://magentocommeng.slack.com/archives/CBSL1DF8B/p1561217992212100
Affected DevDocs pages