Merge Preparation

[zenzeii]

User story

1. As a developer
2. I want to be ready to merge our work to the core repository
3. So that we can smoothly merge our work to the repo of our industry partner

Acceptance criteria

• All documentation needs to be tested and updated if needed.
• All elements that will be merged are being reviewed and documented.
• Things that should not be merged are documented (e.g. build, reports, deliverables etc.)
• Check last years amos merge and document possible problems or look outs (AMOS Project Final PR rtdip/core#862)
• For the Merging we need to follow this documentation: https://github.com/rtdip/core/blob/develop/RELEASE.md Make sure to understand. All questions needs to be asked.
• All MkDocs are ready.
• Review the webpages from MkDocs

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