Skip to content

Development Process

Jump to bottom
Maximilian Ong edited this page Feb 28, 2025 · 5 revisions

Process

BPDM Development Process

The BPDM development process operates in two-week sprints and can be tracked here:
GitHub Project Board

Creating Issues in BPDM

Anyone can create a new issue in the BPDM repository, but please note that issues at this level should be developer-focused.
Each BPDM issue should be linked to a SIG release issue:
https://github.com/eclipse-tractusx/sig-release/issues

What is a SIG Release Issue?

A SIG release issue acts as the equivalent of a Feature in SCRUM.

Why is the Linkage Important?

Linking BPDM issues to SIG release issues is helpful because it:

  1. Organizes Development Efforts – Ensures all related development issues are collected and tracked.
  2. Manages Catena-X Releases – Identifies which items should be included in an official release.
  3. Tracks Dependencies – Helps to recognize dependencies between repositories, improving coordination.

The process in the BPDM project board GitHub Project Board follows these stages:

  1. NEW: A new issue that has not yet been presented in the BPDM refinement meeting.
    The person who creates the issue is responsible for guiding it to the "Refined" status.

  2. Backlog: An issue currently under refinement but not yet ready to be added to the sprint for development.

  3. Refined: An issue that has been fully refined, and developers understand what needs to be done.
    During sprint planning, the issue is assigned to a developer.

  4. In Progress: A developer is actively working on this issue.

  5. In Review: The issue has been fully developed and is being reviewed by others before merging.

  6. Done: The issue is completed, merged, presented in the sprint review meeting, and then archived.

Open Meeting:

Refinement every Wednesday https://eclipse-tractusx.github.io/community/open-meetings

Testing:

Test Cases for SIG Release Issues

SIG Release issues should include basic, easily understandable test cases.

Business Requirements Testing

Execution: Conducted by the Product Owner, which in our case is the SIG Release issue owner.

When? During the E2E testing phase.

BPDM Repository Issues

  • The contributor is responsible for code-based test cases.
  • If possible, automated tests should be written.

Test Execution

  • Automated Tests: Executed immediately after contribution.
  • Manual Tests: The committer verifies the test before merging it into the main branch.

Clone this wiki locally