DOCS-3009: Add the feature status data file - #2928
Merged
Merged
Conversation
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new YAML “source of truth” data file intended to centralize Technology Preview feature-status timelines across Calico Open Source and Calico Enterprise, so release-note tables (and future per-feature status notes) can be generated consistently.
Changes:
- Introduces
data/feature-status.yamlwith a schema and editing guidance (record only status changes; status carries forward). - Captures per-product, per-release status timelines (with provenance metadata and a mechanism to suppress rendering when data is inferred/unconfirmed).
Suppressed comments (1)
data/feature-status.yaml:156
- The file ends with a whitespace-only trailing line, which can create unnecessary diff churn and may trip whitespace-sensitive tooling. Remove the trailing whitespace-only line so the file ends after the last YAML entry.
"3.19": tech-preview # oldest column in any table; may predate 3.19
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Add data/feature-status.yaml, which records the status of each feature per product and release line, across the whole lifecycle: technology preview, generally available, deprecated, and removed. The file records only status changes, and a status carries forward until the next entry. Nothing reads the file yet. It reproduces the technology preview tables in the Calico Open Source 3.30, 3.31, and 3.32 release notes and the Calico Enterprise 3.21, 3.22, 3.23, and 3.24 release notes, with one exception: selector-scoped Felix configuration, which the file records as starting in Enterprise 3.24. The correction to those tables is in DOCS-3011. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ctauchen
force-pushed
the
docs-3009-feature-status-data
branch
from
August 18, 2026 11:25
5705154 to
fbd9c27
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Suppressed comments (2)
data/feature-status.yaml:10
- The note about Enterprise versions is easy to misread as meaning the YAML keys should include the "-1" suffix (for example, "3.24-1"). Since the release-notes table columns are "3.22 | 3.23 | 3.24" (see calico-enterprise_versioned_docs/version-3.24-1/release-notes/index.mdx:67), consider rewording this comment to clearly distinguish the docs version directory name (version-3.24-1) from the table column label (3.24).
# Version keys match the table column labels. Docusaurus adds a suffix to
# Enterprise versions: 3.24-1 is release line 3.24.
data/feature-status.yaml:83
confirmed: falseis currently nested underproducts.calico-enterprise, which mixes metadata with the version->status timeline keys. Ifconfirmedis meant to control whether the feature is rendered, keeping it at the feature level (sibling toname/products) keeps the per-product timelines homogeneous and simplifies future table-generation code.
- id: non-cluster-hosts-vms
name: Non-cluster hosts and VMs
products:
calico-enterprise:
confirmed: false
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.
The status tables are maintained by hand across seven release notes pages and two products. The same feature appears in several tables with different columns, so a status change means editing several tables, and a mistake in one is invisible from the others. This adds a single data file to hold that information, so the tables can be generated from it later.
The file records the whole feature lifecycle, so it drives both the technology preview tables and the deprecated and removed tables. It records only status changes, and a status carries forward until the next entry. A feature that ships in more than one product gets one entry with a per-product timeline.
Nothing reads the file yet.
Changes:
The file reproduces all seven technology preview tables, with one exception: selector-scoped Felix configuration starts in Enterprise 3.24, not 3.23. That correction is in #2927.
DOCS-3009: https://tigera.atlassian.net/browse/DOCS-3009