[tractusx-dev] Invitation: Eclipse Tractus-X Release 26.06 – Release Pla

[Stephan Bauer <stephan.bauer@xxxxxxxxxxxx>]

Hello, Eclipse Tractus-X Community!

Collaboration drives the success of Eclipse Tractus-X, and we are excited to invite you to the Release Planning sessions for R26.06! These sessions are your chance to shape the roadmap, align with the community, and ensure a well-structured release.

Rooms for Discussion and Planning:

• Release Management
• Test Management

Key Information:

• Dates and Times: Listed for each session below.
• Resources: Visit our open meetings page for all session links and additional documentation.
• Preparation Materials: Ensure readiness by reviewing the provided templates, guidelines, and your own features.
• Overall process description: Release Planning Process

We look forward to seeing you there and working together to make R26.06 a success!

Alignment Day for R26.06

The Alignment Day focuses on addressing open questions and unresolved dependencies from features planned for Release 26.06. This meeting is a possibility to connect and clarify open items before the main planning session.

TIP

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

• Date: 12.02.2026
• Time: 09:05 - 10:00
• Main Teams Link: See the Open Meetings page (One-time meetings) for the join link and local-time conversion: Open Meetings

Agenda

INFO

The agenda itself is dependent on the labeled features.

• 09:05 - 09:15: Welcome and overview of Open Discussion features
• 09:15 - 09:55: Group discussions and breakout sessions as needed
• 09:55 - 10:00: (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.06

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

• Date: 26.02.2026
• Time: 09:05 - 12:15 (end time can vary based on discussion and features)
• Teams Link: See the Open Meetings page (One-time meetings) for the join link and local-time conversion: Open Meetings

Who Should Attend:

• Contributors and Committers from the open-source community
• Experts
• 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 and filtered by Topic/Product. The current agenda is only an example and will be updated with the actual features that are planned for R26.06.

Time	Topics	Features
09:05 – 09:20	Open Planning - Vision & Introduction
09:20 – 10:00	Product & Platform Topics
10:00 – 10:30	Sustainability & Use Cases
10:30 – 11:15	Engineering
11:15 – 12:00	Test Management / Misc

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:

• 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.06, 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