Tractus-X 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.
The release of content in Tractus-X is governed by the open source community. The association however takes influence on the planning concerning its interests. The release process for Tractus-X is devided into four phases:
1.Planning
The Preparation Phase is crucial for setting the direction and scope of the release. It ensures all stakeholders align on the planned content. During this phase, all work related to KITs, Reference Implementation, API Specification, Protocols, Sample Data, Architecture, Documentation, Deployment Scripts, or Tutorials should be announced.
Anyone can contribute by creating an issue in Tractus-X. The creator is responsible for refining the proposal until it meets the minimal content requirements for validation. Depending on the feature proposal it needs to be broken down into detailed specifications, addressing any ambiguities, and preparing comprehensive plans that guide the subsequent development and implementation activities. The goal 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.
In the Open Planning, upcoming release items are reviewed, and issues submitted on time are presented. This is the final opportunity for feedback on a proposal's scope. After the presentation, committers will prioritize proposals in coordination with topic owners.
2.Implementation
3.Testing
Test management involves the planning, execution, and monitoring of testing activities to ensure the quality and functionality of software products. Effective test management requires careful planning, execution, and monitoring. By utilizing a wide range of tools and by managing both internal and external dependencies, we can ensure high-quality software releases that meet user expectations and business requirements.
The test management tools are owned by the association and is provided to association members exclusively and not the open source community!