Allocate MCP number for 'Licensing and encryption' #2919
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
hubertus65
approved these changes
Apr 19, 2021
Collaborator
|
Ok by phone meeting. |
Collaborator
Author
|
I'll assume this gets merged in the current state, allocating number 0039, and help @hubertus65 getting started with that number. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
As the good intentions of #2917 are obvious, I'm avoiding unnecessary delays by creating the required PR for MCP number allocation.
For an overview of the proposal, I recommend this document from #2917:
https://github.com/modelica/ModelicaSpecification/blob/origin/MCP/0039/RationaleMCP/0039/SEMLA_Overview_20210225.pdf
I expect that we can vote on this during the upcoming phone meeting.