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 R25.09! These sessions are your chance to shape the roadmap, align with the community, and ensure a well-structured release.
New room in our matrix chat -> Release Management New room in our matrix chat -> 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.
We look forward to seeing you there and working together to make R25.09 a success!
Refinement Day 1 for R25.09
The first Refinement Day sets the foundation for R25.09. Expert groups will brainstorm, refine features, and identify key dependencies for roadmap alignment.
- Date: Wednesday, 09th April 2025
- Time: 09:05 - 12:00
- Main Teams Link: Join the session
Agenda
- 09:05 - 09:30: Welcome, Introduction, and Expectations
- 09:30 - 11:15: Refinement in dedicated groups
- 11:15 - 11:45: Group presentations on progress
- 11:45 - 12:00: Closing and Next Steps
Sessions
Links to the teams sessions for each group will be provided soon. PLease also have a look in the Release Management channel and on the tractusx-dev mailing list.
The sessions are used for refinement day 1 and 2.
Preparation Checklist
- Review the feature template.
- Prepare initial ideas for features.
- Identify potential dependencies with other groups or components.
- Familiarize yourself with related roadmap items.
- Use the supported-by field to map the feature with your expert group
Group and Teams Sessions
During the refinement sessions, each group will focus on the first steps of skeleton-building for their features (based on the feature template), mapping them to the related roadmap items. Don’t worry about completing every section of the feature template just yet — this is a time for brainstorming and forming initial ideas.
It's essential, however, to use the feature template and identify dependencies with other components or groups, which will help us add the correct labels to the features. You’re encouraged to collaborate across groups as needed, and we’ll provide Teams sessions for each group to work in.
The sessions for the different groups / components / dependencies can be used to sync within the underlying expert groups. Feel free to switch between groups if necessary!
Refinement Day 2 for R25.09
The second Refinement Day focuses on resolving dependencies identified during Refinement Day 1. Groups will refine their features further, ensuring alignment across components.
- Date: Wednesday, 30th April 2025
- Time: 09:05 - 12:00
- Main Teams Link: Join the session
Agenda
- 09:05 - 09:30: Welcome and recap of Refinement Day 1 results
- 09:30 - 11:15: Group work on resolving dependencies
- 11:15 - 11:45: Group presentations on resolved dependencies
- 11:45 - 12:00: Closing and Next Steps
Key Focus Areas
- Use the feature template.
- Add labels for identified dependencies.
- Collaborate across groups to resolve issues.
- Use the supported-by field to map the feature with your expert group.
- Status
Backlog-> this should be an alignment, between the requesting Expert Group/Committee and the open-source community.
Group and Teams Sessions
During the refinement sessions, each group will focus on resolving identified dependencies from Refinement Day 1, which are visible via the related labels on the features. While further feature refinement is allowed, the emphasis is on addressing and coordinating dependencies between groups and components.
Our working Board for the day is the Release Planning - R25.09 - Preparation
You’re encouraged to collaborate across groups as needed, and we’ll provide Teams sessions (we will use the same sessions from Refinement Day 1) for each group to work in. It might be the case for some experts to jump into different other groups to resolve dependencies.
The sessions for the different groups / components / dependencies can be used to sync within the underlying expert groups. Feel free to switch between groups if necessary!
Open Planning for R25.09
The Open Planning session finalizes the roadmap for R25.09, prioritizing features and aligning all participants on deliverables for the release.
- Date: Wednesday, 7th May 2025
- Time: 09:05 - 17:00
- 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
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:30: Open Planning - Vision & Introduction
- 09:30 - 16:00: Joint Open Planning (all teams)
- 16:00 - 16:30: Feedback Retro
- 16:30 - 17:00: Open Planning Wrap-Up / Summary & Next Steps
The planning sessions will be driven by our Release Planning Board, which organizes features based on their supported-by field.
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.
- Supported-by must be set.
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.
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! 🚀