docs: publish the 2.0.0 release, lifecycle, and platform compatibility - #16
Merged
Merged
Conversation
2.0.0 ships on 2026-09-08 with a two-year lifecycle and runs on Alauda Container Platform v4.2, v4.3, and v4.4. Replace the "not yet published" placeholders with the published facts: - lifecycle_policy: the version lifecycle timeline (end of full support 2027-09-30, end of maintenance 2028-09-30) plus the release, support-phase, and maintenance policy sections adapted from Alauda Cache Service E1; - release_notes: the compatibility and support matrix, the release date, and the removal of the pending-matrix caveat; - intro, installation, upgrade: current-release wording, the supported platform versions, and the v4.1 exclusion. 2.0.0 has no predecessor product version, so the upgrade procedure applies from the next 2.0.x release. Correct the 9.1 packaging claim. At tag v2.0.0 the canonical custom resource definition under config/crd/bases enumerates 9.1, and the delivered artifact is the OLM bundle generated from it. The stale chart copy under charts/ is referenced by neither the Makefile nor .build/build.yaml and is never installed, so five pages no longer attribute a packaging risk to it. The installed-schema verification step stays. Record the release facts and their evidence class in agent/SOURCE_POLICY.md, agent/CONTENT_AUDIT.md, and agent/ARCHITECTURE_FACTS.md; register the Full Support and Maintenance lifecycle terms in agent/TERMINOLOGY.md; and refresh llms.txt and llmstxt-state.json for the 15 files whose content changed since the index was last generated.
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
1 participant
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.
Cherry-picks
4f877ecfrom #15 (merged torelease-2.0) ontomaster. Applied cleanly with no conflicts; this branch andorigin/release-2.0are now content-identical.Publishes the 2.0.0 release facts for Alauda Cache Service E2, released 2026-09-08 with a two-year lifecycle and support on Alauda Container Platform v4.2, v4.3, and v4.4.
Release facts published
Lifecycle dates follow the Alauda Cache Service E1 convention: release date plus one and two years, rounded to the end of that month.
lifecycle_policy.mdxnow carries the same four sections as E1 — version lifecycle timeline, release policy, support phases (Full Support in year one, Maintenance in year two), and maintenance policy — while keeping the Valkey-specific version dimensions and supported-version rule.Every "not yet published" and "next major release" placeholder is resolved across
lifecycle_policy.mdx,release_notes.mdx,intro.mdx,installation.mdx,upgrade.mdx, andlimitations.mdx. 2.0.0 has no predecessor product version, soupgrade.mdxstates that the procedure applies from the next 2.0.x release onward and points new environments atinstallation.mdx.Correction: the 9.1 "packaging defect" warning
Five pages warned that the Helm Chart custom resource definition copy is stale and that a release package must install the canonical schema before 9.1 can be admitted. Verified at tag
v2.0.0:config/crd/basesenumerates9.1, the chart copy undercharts/does not — but that chart is an upstream directory untouched sinced430d34, referenced by neither theMakefilenor.build/build.yaml, and the delivered artifact is the OLM bundle generated fromconfig/manifests. The warning pointed at a file customers never install, so the narrative is removed; the installed-schema verification step stays.Evidence ledger and index
SOURCE_POLICY.md,CONTENT_AUDIT.md, andARCHITECTURE_FACTS.mdrecord the release facts as evidence class 1 (product-owner requirements with no source-code evidence) together with the lifecycle date convention, the 2.x-only scope, and the corrected image baseline.TERMINOLOGY.mdregisters Full Support, Maintenance, end of full support, end of maintenance, and Alauda Container Platform.llms.txtandllmstxt-state.jsonare refreshed for the 15 files whose sha256 no longer matched the index. All 35 state entries verify against this branch.Verification
yarn lintandyarn buildboth clean on this branch.Follow-ups, not in this change
installation.mdxstill says "chart" twice, and its audit row cites Helm values and templates as evidence, for a page that ships as an OLM bundle. Re-deriving that page against the bundle is a separate task.how_to/30-upgrade.mdxis still unknown — an implementation gap, deliberately kept.valkey-operator/charts/valkey-operator/crds/should be regenerated or removed upstream.🤖 Generated with Claude Code