Repository navigation
feat(i18n): prepare bilingual third-wave extension metadata (no public downloads) - #36
Merged
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
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.
Scope
Stage Japanese translations of the exact future verified Catalog descriptions and Test Contract scenarios of pgTAP, pg_variables and pg_store_plans. The existing
/ja/and/en/routes, per-language switch and actual Catalog index-driven download rendering remain unchanged./en/route.Upstream immutable source pins and Windows CI evidence: pgextwin/build#141 (comment).
Catalog verifier-first intake: pgextwin/catalog#133.
Safety
Wave3 three formal releases are unpublished and Issue #75 GO B/G4/G5 NO-GO; this is localization-only preparation. Existing protected
lifecycle-testsApp15368 must pass before squash merge and postmerge.