Skip to content

Development Process

Jump to bottom
Maximilian Ong edited this page Dec 12, 2024 · 2 revisions

The BPDM development process operates in two-week sprints and can be tracked here:
https://github.com/orgs/eclipse-tractusx/projects/21/views/1

Anyone can create a new issue in the BPDM repository but on this level the issues should be written for developers. Each issue on this level should be linked to a SIG release issue: https://github.com/eclipse-tractusx/sig-release/issues

The process 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.

Clone this wiki locally