Epic Goal

Cleaning up accumulated technical debt throughout the ACM 2.11 / MCE 2.6 release.

Why is this important?

Addressing technical debt is crucial for maintaining the long-term health, stability, and sustainability of our product's code.

Scenarios

...

Acceptance Criteria

• [ ] Conduct a thorough assessment of the codebase to identify and prioritize areas of technical debt, including but not limited to legacy code, outdated dependencies, code smells, and inadequate testing coverage.
• [ ] Implement cleanup initiatives according to the established roadmap, focusing on high-priority technical debt items first. These initiatives may include refactoring legacy code, updating outdated dependencies, improving test coverage, and enforcing coding standards.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.