Roadmap for 2025 and later

[vdemeester]

Starting a discussion to discuss the upcoming 2025 year roadmap as well as how we should manage it.

First, the current roadmap.md file has not been updated for 3 years and is most likely not fully representative of what is planned, …

• I think we need a more dynamic way to manage the roadmap. It could be using a discussion (all maintainers can edit the main body and thus, given discussions, … could add items to the roadmap) or some issue labels + filter + project maybe (? but we tried this before, I don't think anybody uses the projects today).
• We should remove that file and instead discuss the roadmap here (for now) and then figure out where and how we store and update it.

My inital thoughts

• 1.0.0 release
• Release automation
  • Automatic bugfix releases for LTS release branches
  • Merge the 2 pipelines involved in the release into one
  • One click or push-branch-to-release for doing a release (reducing the need to access to the clusters, …)
• tekton bundles and reference (from within)
• git resolver and reference (from within ?)
• Finishing trusted artifact implementation
• Move StepAction to stable
  • GA
  • graduate to v1
• Runtime Matrix (to make them more useful)
  • e.g. heterogeneous cluster to build things
• Pipelines-in-pipelines implementation (TEP-0056)
• Debug PipelineRuns
• Better bigger results support (termination message limits, and sidecarlogs scale are both problematic)
• Some TEP
  • TEP-0036: Start Measuring Tekton Pipelines Performance
  • TEP-0085: Per-namespace configuration
  • TEP-0038: Generic Workspaces
  • TEP-0082: Workspace Hinting
  • TEP-0091: Trusted Resources and TEP-0139: Trusted Artifacts
  • TEP-0120: Canceling Concurrent PipelineRuns and TEP-0132: Queueing Concurrent Runs
  • TEP-0130: Pipeline-level Service
  • TEP-0125: Add credential filter to entrypoint logger
  • TEP-0136: Capture traces for task pod events
  • TEP-0146: Parameters in Script
  • TEP-0154: Concise Remote Resolver Syntax

In addition, there is the label area/roadmap that should help/reflect this.

cc @afrittoli @tektoncd/core-maintainers @tektoncd/core-collaborators

[afrittoli]

Thanks for starting this.

The roadmap project Tekton Community Roadmap (view) and the pipeline v1 project Pipelines V1 have been kept more up to date than then markdown 😅

I agree that a 1.0 release is first on the list.

Recently a lot of work has gone into reducing infra costs, and I think that will continue for some more time.
Streamlining project maintenance work is another important topic, which includes the bug fix releases from your list.

• we should have a regular schedule of automated patch releases in between LTS releases
• where possible, we should factor up release and test StepActions or Tasks across projects
• the release pipeline should be merged from the current two steps process to a fully automated single pipeline

Move StepAction to stable is a good one, that should not take much work and would be very beneficial.
Pipelines-in-pipelines is a highly requested feature and it would be good to have it implemented. Like all other features you mentioned, we'll need someone to take-on the implementation. I'd be happy to mentor and review on most of the things in the list.

[vdemeester]

@afrittoli Do you see anything more to add to the list ?

What we could do, from this discussion, is to make sure we have issues for each items, correctly labeled with area/roadmap (and added to the project) so that it appears on Tekton Community Roadmap (view) (that looks good I think).

I'll add the release part to the list (and then will create issue if they are not existing in the repo)