Skip to content

Commit 3dbf778

Browse files
Merge pull request #1257 from eclipse-tractusx/docs/update-open-planning
docs(open planning): adapt open planning information
2 parents cedeecd + 9506ed1 commit 3dbf778

File tree

1 file changed

+32
-6
lines changed

1 file changed

+32
-6
lines changed

blog/2025-03-20-release-planning-R25.09.mdx

Lines changed: 32 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The sessions are used for refinement day 1 and 2.
6161
- Prepare initial ideas for features.
6262
- Identify potential dependencies with other groups or components.
6363
- Familiarize yourself with related roadmap items.
64-
- Use the supported-by field to map the feature with your expert group
64+
- Use the `Topic/Product` field to map the feature with your expert group
6565

6666
### Group and Teams Sessions
6767

@@ -127,11 +127,37 @@ feature requesters are encouraged to attend and actively engage in the discussio
127127

128128
Here’s the plan for the day:
129129
- **09:05 - 09:30**: Open Planning - Vision & Introduction
130-
- **09:30 - 16:00**: Joint Open Planning (all teams)
131-
- **16:00 - 16:30**: Feedback Retro
132-
- **16:30 - 17:00**: Open Planning Wrap-Up / Summary & Next Steps
130+
- **09:30 - 14:00**: Joint Open Planning (all teams)
131+
- **14:00 - 14:30**: Feedback Retro / Open Planning Wrap-up / Summary & Next Steps
133132

134-
The planning sessions will be driven by our [Release Planning Board](https://github.com/orgs/eclipse-tractusx/projects/26/views/28?filterQuery=-status%3ADone+has%3Asupported-by+label%3A%22Prep-R25.09%22+status%3ABacklog), which organizes features based on their **supported-by** field.
133+
#### Joint Open Planning
134+
135+
:::note
136+
The planning sessions will be driven by our [Release Planning Board](https://github.com/orgs/eclipse-tractusx/projects/26/views/28), which organizes features based on their **Topic/Product** field.
137+
:::
138+
139+
| Time | Committee | Features |
140+
|-------------------|-------------------------------------------|----------|
141+
| 09:30 09:35 | DPP | 1 |
142+
| 09:35 09:45 | Circularity | 2 |
143+
| 09:45 10:45 | Dataspace Connectivity | 10 |
144+
| 10:45 11:15 | BPDM | 5 |
145+
| 11:15 11:20 | Digital Twin (DT) | 1 |
146+
| 11:20 11:25 | SSI | 1 |
147+
| 11:25 12:00 | Portal | 7 |
148+
| 12:00 13:00 | Lunch Break | |
149+
| 13:00 13:10 | Traceability | 2 |
150+
| 13:10 13:20 | DCM | 2 |
151+
| 13:20 13:30 | PURIS | 2 |
152+
| 13:30 13:40 | Industry Core | 2 |
153+
| 13:40 13:50 | Digital Twin | 1 |
154+
| 13:50 13:55 | Testmanagement | 1 |
155+
| 13:55 14:00 | Engineering | 1 |
156+
157+
:::warning[**Please note:**]
158+
- The agenda provides a **rough time structure** to help guide the session. The **timings are not fixed** and can be adjusted depending on the flow of the discussion.
159+
- Use the agenda as **orientation**, but we may deviate if needed based on progress.
160+
:::
135161

136162
### Prerequisites for features to be considered in Open Planning
137163

@@ -140,7 +166,7 @@ For a feature to be included in the Open Planning, the following conditions must
140166
- **All categories in the feature template must be filled** Do not delete any sections from the template.
141167
- **Milestone is NOT set** This will be assigned during the Open Planning session.
142168
- **Contributor and Committer must be assigned**.
143-
- **Supported-by must be set**.
169+
- **`Topic/Product` must be set**.
144170

145171
During the session, if there is a common alignment among the participants, the feature milestone can be set to **25.09**, meaning it will be developed in the upcoming release.
146172

0 commit comments

Comments
 (0)