[tractusx-dev] Alignment Day (this Thirsday day)& Open Planning Day (Nov

[Stephan Bauer <stephan.bauer@xxxxxxxxxxxx>]

Hi everyone,

a quick reminder that our Alignment Day and Open Planning Day for the R26.03 cycle are coming this Thursday and in November (please take a look at the news blog and the open meetings):

Alignment Day for R26.03

The Alignment Day focuses on addressing open questions and unresolved dependencies from features planned for Release 26.03. This means we are highly dependent on your questions. We want to align and get a better understanding about the related features. This meeting is a possibility to connect. Label `Prep-R26.03` MUST be set

TIP

Even if you don't have questions, it could be interesting anyway.

• Date: 30.10.2025
• Time: 09:05 - 10:45
• Main Teams Link: Join the session

Agenda

INFO

The agenda itself is dependent on the labeled features.

• 09:05 - 09:20: Welcome and overview of Open Discussion features
• 09:20 - 10:30: Group discussions and breakout sessions as needed
• 10:30 - 10:45: (Optional) closing and documentation of decisions

Key Focus Areas

• Only features labeled open question will be considered for the agenda.
• The label must be added at least 3 days prior to the event.
• This is not a planning or refinement session — it’s a space to align on open questions and clarify remaining uncertainties.
• Feature owners should be ready to describe their needs or concerns.
• Component developers can use this session to clarify what is expected from them.

Open Planning for R26.03

The Open Planning session finalizes the roadmap for R26.03, prioritizing features and aligning all participants on deliverables for the release.

• Date: 13.11.2025
• Time: 09:05 - 12:15
• Teams Link: Join the session

Who Should Attend:

• Contributors and Committers from the open-source community
• Expert Group and Committee members
• Feature requesters and stakeholders

NOTE

Your participation is crucial to ensure the success of the release planning. Expert Groups, Committees, the open-source community (contributor and committer), feature requesters are encouraged to attend and actively engage in the discussions.

Agenda

Here’s the plan for the day:

• 09:05 - 09:20: Open Planning - Vision & Introduction
• 09:20 - 12:00: Joint Open Planning (all teams)
• 12:00 - 12:15: Feedback Retro / Open Planning Wrap-up / Summary & Next Steps

Joint Open Planning

NOTE

The planning sessions will be driven by our Release Planning Board, which organizes features based on their Topic/Product field. The current agenda is only an example and will be updated with the actual features that are planned for R26.03.

Time	Topics	Features
09:05 – 09:20	Open Planning - Vision & Introduction	Link
09:20 – 09:25	PCF	Link
09:25 – 09:35	Circularity	Link
09:35 – 10:10	Dataspace Connectivity	Link
10:10 – 10:30	BPDM	Link
10:30 – 10:50	Portal	Link
10:50 – 11:05	SSI	Link
11:05 – 11:15	Traceability	Link
11:15 – 11:25	DCM	Link
11:25 – 11:30	OSIM	Link
11:30 – 11:35	PURIS	Link
11:35 – 11:50	Industry Core	Link
11:50 – 11:55	Digital Twin	Link
11:55 – 12:00	Testmanagement	Link
12:00 – 12:15	Miscellaneous and Closing	Link

PLEASE NOTE

• 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.
• Use the agenda as orientation, but we may deviate if needed based on progress.

Prerequisites for features to be considered in Open Planning

For a feature to be included in the Open Planning, the following conditions must be met:

• Label `Prep-R26.03` MUST be set
• Status must be `Backlog – Committers and Expert Groups can set this status after the feature is fully refined.
• All categories in the feature template must be filled – Do not delete any sections from the template.
• Milestone is NOT set – This will be assigned during the Open Planning session.
• Contributor and Committer must be assigned.
• Topic/Product must be set.

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

Important Notes and Hints

• Keep the board clean – there are still features with older milestones that have not yet been completed.
• Do not delete any sections from the feature template, except for KITs.
• For KITs, only the Contributor, Committer, and Description fields need to be filled.

For any questions or further information, feel free to reach out via our mailing list or join us in the Tractus-X Matrix channel.

We look forward to your participation and collaboration! 🚀

Stephan Bauer 

Eclipse Tractus-X Project Lead