Clarify Decision Point Versioning rules (revises ADR 0003 into ADR 0006) #369
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
ahouseholder
requested review from
cgyarbrough,
sei-vsarvepalli and
j---
as code owners
j---
approved these changes
Nov 7, 2023
ahouseholder
merged commit d3058cd
into
355-create-adrs-for-decision-point-group-versioning
ahouseholder
added a commit
that referenced
this pull request
Nov 7, 2023
* add adrs * typo fix * make logic explicit * indent logic in lieu of parentheses * Clarify Decision Point Versioning rules (revises ADR 0003 into ADR 0006) (#369) * revise ADR 0003 into ADR 0006 * fix header
ahouseholder
deleted the
367-adr-0003-fails-to-address-how-changes-to-decision-point-metadata-affects-versioning
branch
This was referenced Nov 7, 2023
ahouseholder
added
documentation
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 PR updates the decision point versioning rules to reflect the discussion on PR #343 that led to Issue #367. It also adapts a format consistent with that of PR #368 w.r.t. the versioning rules presentation.
Doing this as a PR against another PR #368 for the sake of ADR number sequencing.
In the event that PR #368 is rejected, this change should be re-targeted at
main.