Tractus-X - From Idea to Release
The development of open source components in Tractus-X is a collaborative effort between the association bodies (Committees and Expert Groups) and the open source community. The association bodies ensure that feature requests align with the strategic goals of the project, meanwhile, the open source community ensures the delivery high-quality code. Together, they ensure the interests of Catena-X and Eclipse Tractux-X are consirdered and respected.
Phase 1: Preparation
The Preparation Phase is the foundational phase that sets the direction and scope for the entire release. It ensures that all stakeholders have a shared understanding of the release's content.
All planned work on Kits, Reference Implementation, API Specification, Protocols, Sample Data, Architecture, Documentation, Deployment Scripts or Tutorials should be announced during this phase.
Preparation ToDo's
Preparation Milestones
Phase 2: Planning
This phase involves breaking down high-level requirements into detailed specifications, addressing any ambiguities, and preparing comprehensive plans that guide the subsequent development and implementation activities. The goal of this phase is to ensure that all aspects of the project are clearly understood, accurately defined, and ready to be built, reducing the risk of issues during the implementation phase.
Planning ToDo's
Planning milestones
Phase 3: Development
The development and release phase includes the development of the software and KITs. The individual units are developed and tested in up to six increments. This is followed by final integration and end-to-end test for the software.
Development ToDo's
Development milestones
FAQs
How are the open meetings communicated? The Catena-X association will communicate and coordinate the open refinement and open planning meetings vi the a Tractus-X News Page and the Tractus-X Mailing List. Please make sure that you subscribe. The meetings will also be published (with meeting session and calender.ics) on the open meetings page.
Who can propose a feature? Anyone can propose a feature, including Committees, Expert Groups, and other initiatives. However, we require a dedicated feature author for further refinement and the breakdown into implementation issues.
How to handle dependencies? Dependencies can be discussed in our open refinement meetings as well as via our other communication channels (e.g. matrix chat or bilateral sessions). Please refer to our Tractus-X communication rules.
Who gives access to the sig-release repository to enable planning process? Please refer to our Tractus-X Getting Started Guide.