Repository navigation
docs(meissa): mark merged M1 and M3 migration tasks (RIG-5901) - #68
Merged
Merged
Conversation
|
Rigel public design docs preview: https://go-migration-rig-5901-meissa-1ife.docs-2ui.pages.dev Deployed from |
Contributor
Author
|
Review all-clear on |
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
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.
Summary
Ticks M1a, M1b and M3 in the meissa migration record. Their PRs (meissa#46, #47, #51) merged. M2 stays open until the first
go/v*tag ships.Verification
Ledger-impact: none. Completion checklist only; no decision changes.
Spec-impact: none. Records completed implementation only.
Refs RIG-5901, RIG-8118, RIG-8119, RIG-8121
Owner: go-migration