You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .kiro/steering/docs.md
+17-7Lines changed: 17 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,18 +376,28 @@ table_order:
376
376
377
377
### Support Policy Consolidation
378
378
379
-
The `framework_groups` configuration consolidates support policy rows by framework. Repositories in the same group are combined into a single row using the framework name (e.g., "PyTorch").
379
+
The `framework_groups` configuration consolidates support policy rows by framework. Repositories in the same group are combined into a single row using the framework name (e.g., "PyTorch") when they share the same GA/EOP dates.
380
380
381
381
**Version Display:**
382
382
383
-
- Images with the same major.minor version (e.g., `2.6.0` and `2.6.1`) are consolidated into a single row displayed as `2.6` if they have identical GA/EOP dates
384
-
- If patch versions have different GA/EOP dates, each is displayed separately with full version (e.g., `2.6.0`, `2.6.1`) and a warning is logged
383
+
- Images with the same major.minor version and identical GA/EOP dates are consolidated into a single row displayed as `2.6` with the framework group name (e.g., "PyTorch")
384
+
- If the same version has different GA/EOP dates across repository types (e.g., training vs inference), separate rows are created showing the specific repository type: "PyTorch Training" and "PyTorch Inference"
385
+
- ARM64 variants are automatically consolidated with their base repository (e.g., "PyTorch Training" and "PyTorch Training ARM64" both show as "PyTorch Training")
386
+
- If patch versions within the same repository have different GA/EOP dates, each is displayed separately with full version (e.g., `2.6.0`, `2.6.1`) and a warning is logged
385
387
386
-
**Requirements:**
388
+
**Behavior:**
387
389
388
-
- All repositories in a group that have a given full version (X.Y.Z) must have identical GA/EOP dates
389
-
- Missing versions in some repositories are allowed (only present repos are consolidated)
390
-
- A `ValueError` is raised if dates differ within a group for the same full version
390
+
- Repositories in the same framework group can have different GA/EOP dates for the same version (e.g., inference can have a different EOP than training)
391
+
- When dates match across all repositories in a group, they are consolidated into a single row with the framework group name
392
+
- When dates differ by repository type (training vs inference), separate rows show the specific repository type names
393
+
- Missing versions in some repositories are allowed (only present repos are included)
394
+
395
+
**Example:**
396
+
397
+
If PyTorch 2.6 Training has EOP 2025-10-15 but PyTorch 2.6 Inference has EOP 2026-10-15, the support policy table will show:
Copy file name to clipboardExpand all lines: docs/DEVELOPMENT.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,10 +81,14 @@ eop: "2035-10-15" # End of Patch date
81
81
82
82
**Version Consolidation:**
83
83
84
-
- Images with the same major.minor version (e.g., `2.6.0` and `2.6.1`) are consolidated into a single row displayed as `2.6` if they have identical GA/EOP dates
85
-
- If patch versions have different GA/EOP dates, each is displayed separately with full version (e.g., `2.6.0`, `2.6.1`) and a warning is logged
84
+
- Images with the same major.minor version and identical GA/EOP dates are consolidated into a single row displayed as `2.6` with the framework group name (e.g., "PyTorch")
85
+
- If the same version has different GA/EOP dates across repository types (e.g., training vs inference), separate rows are created showing the specific repository type: "PyTorch Training"and "PyTorch Inference"
86
+
- ARM64 variants are automatically consolidated with their base repository
87
+
- If patch versions within the same repository have different GA/EOP dates, each is displayed separately with full version (e.g., `2.6.0`, `2.6.1`) and a warning is logged
86
88
87
-
**Validation:** All images in the same framework group with the same full version (X.Y.Z) must have identical GA/EOP dates.
89
+
**Flexibility:** Repositories in the same framework group (e.g., pytorch-training and pytorch-inference) can have different GA/EOP dates for the same version. The system will automatically create separate rows showing the specific repository type when dates differ.
90
+
91
+
**Example:** If PyTorch 2.6 Training has EOP 2025-10-15 but PyTorch 2.6 Inference has EOP 2026-10-15, the support policy table will show two separate rows with "PyTorch Training" and "PyTorch Inference" in the Framework column.
0 commit comments