Skip to content

Commit d9df4b3

Browse files
vdemeestervdemeester
committed
docs: Document roadmap project board workflows and best practices
- Fix incorrect project link and remove outdated 2021 roadmap - Explain how items are automatically added via area/roadmap label - Document automated status transitions from GitHub project workflows - Add best practices for contributors and maintainers Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
1 parent 7783005 commit d9df4b3

File tree

1 file changed

+104
-57
lines changed

1 file changed

+104
-57
lines changed

‎roadmap.md‎

Lines changed: 104 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -1,63 +1,110 @@
11
# Tekton Pipelines Roadmap
22

3-
Our community roadmap can be found [here](https://github.com/orgs/tektoncd/projects/26/views/16).
4-
This project automatically includes issues and PRs with label `area/roadmap`.
3+
**Project Board:** https://github.com/orgs/tektoncd/projects/16
4+
5+
## Purpose
6+
7+
The Tekton Pipelines Roadmap project board tracks the development roadmap for the `tektoncd/pipeline` component. It provides visibility into planned features, ongoing work, and completed items including:
8+
9+
- Feature requests and enhancements
10+
- TEPs (Tekton Enhancement Proposals)
11+
- Epics and their sub-issues
12+
- Infrastructure improvements
513

614
See [The Tekton mission and vision](https://github.com/tektoncd/community/blob/main/roadmap.md#mission-and-vision)
715
for more information on our long-term goals.
816

9-
## 2021 Roadmap
10-
11-
*2021 Roadmap appears below for historic purposes.*
12-
13-
* [v1 API](https://github.com/tektoncd/pipeline/issues/3548)
14-
* Support alpha fields within v1 and beta types ([TEP-0033](https://github.com/tektoncd/community/blob/main/teps/0033-tekton-feature-gates.md))
15-
* When expressions:
16-
* Option to skip Task only ([TEP-0007](https://github.com/tektoncd/community/blob/main/teps/0007-conditions-beta.md#skipping-1))
17-
* [Support in Finally Tasks](https://github.com/tektoncd/pipeline/issues/3438) ([TEP-0045](https://github.com/tektoncd/community/blob/main/teps/0045-whenexpressions-in-finally-tasks.md))
18-
* [Env vars at runtime](https://github.com/tektoncd/pipeline/issues/1606)
19-
* Workspaces/PVCs/Affinity Assistant ([TEP-0046](https://github.com/tektoncd/community/pull/318)
20-
* [Investigate custom scheduler for PVCs](https://github.com/tektoncd/pipeline/issues/3052)
21-
* [OCI bundles to beta](https://github.com/tektoncd/pipeline/issues/3661) (and then v1)
22-
* Expanded expression support via [CelRun Task](https://github.com/tektoncd/pipeline/issues/3149)
23-
* [Pipelines in Pipelines](https://github.com/tektoncd/pipeline/issues/2134)
24-
* Support for more complex failure scenarios
25-
* Allow task failure ([TEP-0050](https://github.com/tektoncd/community/pull/342))
26-
* Allow step failure ([TEP-0040](https://github.com/tektoncd/community/pull/302))
27-
* Decisions regarding more complex graph construction on failure
28-
* [Instrument Tekton resources](https://github.com/tektoncd/pipeline/issues/2814)
29-
* Minimize overhead of running a pipeline
30-
* Improve ability to compose Tasks with Tasks ([TEP-0044](https://github.com/tektoncd/community/pull/316))
31-
* [Workspaces “from” other Tasks (express resource dependencies on workspaces)](https://github.com/tektoncd/pipeline/issues/3109)
32-
* [Custom Tasks](https://github.com/tektoncd/community/blob/main/teps/0002-custom-tasks.md) completion:
33-
* [Pipeline Results](https://github.com/tektoncd/pipeline/issues/3595)
34-
* Example controller for folks who want to create custom tasks
35-
* Experimental custom tasks promotion (e.g. [CELRun](https://github.com/tektoncd/experimental/tree/main/cel)):
36-
* Plan around how to promote (what requirements, process)
37-
* Continuous integration + release automation
38-
* Documentation and examples at tekton.dev
39-
* Integration with operator
40-
* [Adding support for other architectures](https://github.com/tektoncd/pipeline/issues/856)
41-
* [Improve UX of getting credentials into Tasks](https://github.com/tektoncd/pipeline/issues/2343) - nearly complete
42-
via [TEP-0029](https://github.com/tektoncd/community/blob/main/teps/0029-step-workspaces.md)
43-
* [Notifications](https://github.com/tektoncd/pipeline/issues/1740)
44-
* [Performant Tekton](https://github.com/tektoncd/pipeline/issues/540)
45-
([TEP-0036](https://github.com/tektoncd/community/blob/main/teps/0036-start-measuring-tekton-pipelines-performance.md))
46-
* [Debug mode](https://github.com/tektoncd/pipeline/issues/2069)
47-
* [PipelineResources: beta or bust](https://github.com/tektoncd/pipeline/issues/1673)
48-
([some discussion and analysis](https://docs.google.com/document/d/1Et10YdBXBe3o2x6lCfTindFnuBKOxuUGESLb__t11xk/edit#heading=h.xz4bckr3atww))
49-
* [Looping syntax](https://github.com/tektoncd/pipeline/issues/2050)
50-
* [Concurrency limits](https://github.com/tektoncd/experimental/issues/699)
51-
([TEP-0013](https://github.com/tektoncd/community/pull/228))
52-
* [Partial Pipeline execution](https://github.com/tektoncd/pipeline/issues/50)
53-
* [Testing tools](https://github.com/tektoncd/pipeline/issues/1289)
54-
* Decisions around what to do with SCM support and the images released as part of Tekton Pipelines to support
55-
[PipelineResources](https://github.com/tektoncd/pipeline/issues/1673)
56-
* [Rich type support for Params](https://github.com/tektoncd/pipeline/issues/1393)
57-
* Decide if these are in scope for Tekton Pipelines:
58-
* [Local execution](https://github.com/tektoncd/pipeline/issues/235)
59-
(and [tektoncd/community#145](https://github.com/tektoncd/community/issues/145))
60-
* [Config as code](https://github.com/tektoncd/pipeline/issues/859)
61-
([TEP-0048](https://github.com/tektoncd/community/pull/341),
62-
[task references via git](https://github.com/tektoncd/pipeline/issues/2298))
63-
* [Rework PipelineRun and TaskRun Status](https://github.com/tektoncd/pipeline/issues/3792)
17+
## Status Columns
18+
19+
| Status | Meaning |
20+
|--------|---------|
21+
| **Todo** | Planned work, not yet started |
22+
| **In Progress** | Actively being worked on |
23+
| **Review** | Implementation complete, awaiting review |
24+
| **Done** | Completed and closed |
25+
| **Hold** | Paused or blocked |
26+
27+
## How Items Get Added
28+
29+
### Automatic Addition (Recommended)
30+
31+
Add the `area/roadmap` label to any open issue or PR in `tektoncd/pipeline`. The automation will:
32+
1. Add the item to the project board
33+
2. Set its status to **Todo**
34+
35+
Sub-issues of items already on the board are automatically added as well.
36+
37+
### Manual Addition
38+
39+
Maintainers can manually add items via the project board interface for items that don't have the `area/roadmap` label.
40+
41+
## How Items Move
42+
43+
Most status transitions happen automatically based on GitHub events:
44+
45+
```
46+
┌─────────────────────────────────────────────────────────────────┐
47+
│ ENTRY POINTS │
48+
├─────────────────────────────────────────────────────────────────┤
49+
│ Label "area/roadmap" added ───────────────► Todo │
50+
│ Sub-issue created ───────────────► Todo │
51+
│ Manually added to project ───────────────► Todo │
52+
└─────────────────────────────────────────────────────────────────┘
53+
│
54+
▼
55+
┌─────────────────────────────────────────────────────────────────┐
56+
│ AUTOMATED TRANSITIONS │
57+
├─────────────────────────────────────────────────────────────────┤
58+
│ │
59+
│ Todo │
60+
│ │ │
61+
│ │ PR linked to issue │
62+
│ │ Changes requested on PR │
63+
│ ▼ │
64+
│ In Progress │
65+
│ │ │
66+
│ │ Issue closed │
67+
│ │ PR merged │
68+
│ ▼ │
69+
│ Done │
70+
│ │ │
71+
│ │ Issue reopened ──────────────────────► In Progress │
72+
│ │ │
73+
│ │ Closed > 1 year with no updates │
74+
│ ▼ │
75+
│ [Archived] │
76+
│ │
77+
├─────────────────────────────────────────────────────────────────┤
78+
│ MANUAL TRANSITIONS │
79+
├─────────────────────────────────────────────────────────────────┤
80+
│ Any status ◄──────────────────────────────► Hold │
81+
│ In Progress ──────────────────────────────► Review │
82+
└─────────────────────────────────────────────────────────────────┘
83+
```
84+
85+
## Best Practices
86+
87+
### For Contributors
88+
89+
| Action | How |
90+
|--------|-----|
91+
| **Get your feature on the roadmap** | Add `area/roadmap` label to your issue |
92+
| **Signal you're working on something** | Link your PR to the issue — status moves to "In Progress" automatically |
93+
| **Break down large features** | Use GitHub sub-issues; they're auto-added to the board |
94+
| **Check what's planned** | Review the Todo column before proposing duplicate work |
95+
96+
### For Maintainers
97+
98+
| Action | How |
99+
|--------|-----|
100+
| **Prioritize roadmap items** | Use the board's drag-and-drop to reorder within columns |
101+
| **Block work temporarily** | Move items to Hold manually; add a comment explaining why |
102+
| **Signal review needed** | Move items to Review manually when implementation is complete |
103+
| **Keep the board clean** | Items auto-archive after 1 year closed, but you can archive manually |
104+
| **Track epic progress** | Use sub-issues — the board shows sub-issue completion progress |
105+
106+
### Things to Avoid
107+
108+
- **Don't manually set Done** — let the automation handle it when issues close or PRs merge
109+
- **Don't remove `area/roadmap` label** to remove from board — the item stays; archive it instead if needed
110+
- **Don't duplicate items** — search the board before adding new roadmap items

0 commit comments

Comments
 (0)