Implementation:Kubeflow Kubeflow WG Tracking Issues

Knowledge Sources	Kubeflow ROADMAP.md Lines 3-23 Trainer Tracking Issue #2859 KServe v0.15.2 Release
Domains	Release Management, Feature Tracking, GitHub Issues
Last Updated	2026-02-13 00:00 GMT

Overview

Concrete tool for tracking feature development across multiple Working Groups, provided by per-WG GitHub tracking issues and GitHub Project Board item management.

Description

WG Tracking Issues are GitHub issues created in each sub-project repository to serve as the authoritative list of features, bug fixes, and enhancements that a Working Group plans to deliver for a given Kubeflow release. Each tracking issue uses a checklist format and is linked to the central release GitHub Project Board for cross-WG visibility. The ROADMAP.md file in the kubeflow/kubeflow repository aggregates these tracking issues with theme-based groupings to provide a unified view.

Usage

Use this implementation when:

• A new release cycle has been planned and tracking issues need to be created
• Working Groups need to report their planned contributions for a release
• The release team needs to monitor progress across all sub-projects
• Features need to be assessed for readiness at feature freeze milestones

Code Reference

Source Location

• Repository: kubeflow/kubeflow
• File: ROADMAP.md (Lines 3-23, v1.11 section)

Signature

# Per-WG Tracking Issue Pattern
gh issue create --repo kubeflow/{sub-project} \
  --title "[vX.Y] {WG Name} Release Tracking" \
  --body "## Features planned for Kubeflow vX.Y
- [ ] Feature A
- [ ] Feature B
- [ ] Bug fix C"

# GitHub Project Board Item Management
gh project item-add {PROJECT_NUMBER} --owner kubeflow --url {ISSUE_URL}

Import

# Access existing tracking issues for v1.11
# Trainer WG:
gh issue view 2859 --repo kubeflow/trainer

# View KServe release:
gh release view v0.15.2 --repo kserve/kserve

# View Katib release:
gh release view v0.19.0 --repo kubeflow/katib

# View Pipelines release:
gh release view 2.15.0 --repo kubeflow/pipelines

# View Model Registry release:
gh release view v0.3.4 --repo kubeflow/model-registry

# View Spark Operator release:
gh release view v2.4.0 --repo kubeflow/spark-operator

I/O Contract

Inputs

Name	Type	Required	Description
release_plan	document	Yes	The approved release plan with version number, timeline, and themes
wg_roadmaps	list of documents	Yes	Individual Working Group roadmaps listing planned features
tracking_issue_urls	list of URLs	Yes	Links to per-WG tracking issues in sub-project repositories
theme_grouping	list of strings	Yes	Theme names for grouping features (e.g., Trainer V2.0, Model Registry new features)
component_version_targets	map of string to string	Yes	Per-component version targets (e.g., KServe: v0.15.2, Katib: v0.19.0)
release_team	list of GitHub handles	Yes	Assigned release team members responsible for monitoring progress

Outputs

Name	Type	Description
implemented_features	list of merged PRs	Features merged across sub-project repositories during the release cycle
updated_tracking_issues	list of URLs	WG tracking issues with checked-off completed items and status annotations
component_releases_tagged	list of URLs	Tagged releases in each sub-project repository (e.g., KServe v0.15.2, Katib v0.19.0)
project_board_status	dashboard	Updated GitHub Project Board reflecting completion status of all tracked items

Usage Examples

Example: Creating Tracking Issues for v1.11

# Create Trainer WG tracking issue
gh issue create --repo kubeflow/trainer \
  --title "[v1.11] Trainer WG Release Tracking" \
  --body "## Trainer features for Kubeflow v1.11

### Theme: Trainer V2.0
- [ ] Implement new Trainer V2 API
- [ ] Migrate existing training jobs to V2 runtime
- [ ] Update documentation for V2 breaking changes

### Bug fixes
- [ ] Fix distributed training timeout issue
- [ ] Resolve memory leak in job controller"

# Create Model Registry WG tracking issue
gh issue create --repo kubeflow/model-registry \
  --title "[v1.11] Model Registry WG Release Tracking" \
  --body "## Model Registry features for Kubeflow v1.11

### Theme: Model Registry new features
- [ ] Add model versioning metadata support
- [ ] Implement artifact lineage tracking
- [ ] REST API v2 endpoints

### Bug fixes
- [ ] Fix pagination in list models endpoint"

Example: Linking Tracking Issues to Project Board

# Add each WG tracking issue to the central release project board
gh project item-add 42 --owner kubeflow \
  --url https://github.com/kubeflow/trainer/issues/2859

gh project item-add 42 --owner kubeflow \
  --url https://github.com/kubeflow/katib/issues/XXXX

gh project item-add 42 --owner kubeflow \
  --url https://github.com/kubeflow/pipelines/issues/XXXX

gh project item-add 42 --owner kubeflow \
  --url https://github.com/kubeflow/model-registry/issues/XXXX

gh project item-add 42 --owner kubeflow \
  --url https://github.com/kubeflow/spark-operator/issues/XXXX

Example: Checking Progress Across WGs

# View the status of all v1.11 tracking issues
gh issue list --repo kubeflow/trainer --search "[v1.11]" --state open
gh issue list --repo kubeflow/katib --search "[v1.11]" --state open
gh issue list --repo kubeflow/pipelines --search "[v1.11]" --state open
gh issue list --repo kubeflow/model-registry --search "[v1.11]" --state open
gh issue list --repo kubeflow/spark-operator --search "[v1.11]" --state open

# View the release project board summary
gh project view 42 --owner kubeflow

Example: v1.11 Tracking Issue Links from ROADMAP.md

# Known tracking issues and releases for Kubeflow v1.11:
# Trainer:        https://github.com/kubeflow/trainer/issues/2859
# KServe:         https://github.com/kserve/kserve/releases/tag/v0.15.2
# Katib:          https://github.com/kubeflow/katib/releases/tag/v0.19.0
# Pipelines:      https://github.com/kubeflow/pipelines/releases/tag/2.15.0
# Model Registry: https://github.com/kubeflow/model-registry/releases/tag/v0.3.4
# Spark Operator: https://github.com/kubeflow/spark-operator/releases/tag/v2.4.0

Related Pages

Implements Principle

• Principle:Kubeflow_Kubeflow_Feature_Development_Tracking