Conformance clarification for region name/area types #290
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
…es/area_types to allow use of flag_values and flag_meanings as per discussion in #198
Contributor
|
Hi @RosalynHatcher Thanks for this. As this original discussion was concluded and agreed, I don't think we need to wait the usual three weeks before merging this - it's essentially a housekeeping task, now. Could you make a note of a link to the unmerged PR in the old conformance repo, for the record? |
Contributor
Author
|
Original PR in the conformance repos is cf-convention/Conformance#10 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Clarification to conformance document for region names/area_types to allow use of flag_values and flag_meanings as per discussion in #198. This was a PR that got missed before the conformance document was moved into the cf-conventions repository.
See issue #198 for discussion of these changes.
Release checklist
cf-conventions.adoc?cf-conventions.adocup to date? Versioning inspired by SemVer.history.adocup to date?For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then
masteralways is a draft for the next version.