correct multi-license introductory description#8800
Merged
kcondon merged 3 commits intoIQSS:developfrom Jul 22, 2022
Merged
Conversation
pdurbin
reviewed
Jun 13, 2022
Member
pdurbin
left a comment
pdurbin
left a comment
There was a problem hiding this comment.
Overall looks good. I left a couple comments.
scolapasta
approved these changes
Jul 20, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What this PR does / why we need it:
Clarifies language concerning which licenses are available to new or existing/upgraded installations.
Which issue(s) this PR closes:
Closes #8791
Special notes for your reviewer:
Run this by @qqmyers
Suggestions on how to test this:
Verify this description of available licenses is correct on new and upgraded installations.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
no
Is there a release notes update needed for this change?:
no
Additional documentation:
none