Merge Project to Core Repository based on Shell Feedback (Part 2)

[SirGankalot]

User story

1. As a developer
2. I want the complete project developed in the forked repository to be merged into the core repository
3. So that the project merge completed and delivered within the core codebase.

Acceptance criteria

• Continuation of Merge Project to Core Repository and Adjust based on Shell Feedback #122
• All acceptance criteria defined in #115 are met and remain valid at the time of merge.
• The merge complies with the release process described in the RTDIP core documentation: https://github.com/rtdip/core/blob/develop/RELEASE.md , and all open questions have been clarified.
• The merge has been communicated to and explicitly agreed upon by the industry partners.
• Update the branch before merging based on newest release
• Not just merge, but adjust also based on shell feedback
• This excludes the possible issues with imports (please still inform the devs who work on Review Possible Fixes for Import Issues #116 and keep a close communication and coordination)

Definition of done (DoD)

• Acceptance criteria are met.
• Work are pushed to the Github repository.
• Create a branch for each backlog items (coding)
• A pull request is created for each related branch.
• The work products in the pull requests are reviewed.
• The corresponding branches are merged and closed.
• The bill of materials section of the planning documents is updated.
• The software architecture should be updated based on features changes.
• Work needs to be documented in the corresponding wiki section
• For new features unit test have to be written.
• Update our forked repository with the latest RTDIP release.
• All unit tests must pass successfully in the CI pipeline.
• If the task involves coding, the implementation is integrated into the RTDIP framework and verified to function correctly within it.

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release