The RM_Release (Release V2) plugin is deprecated, and the process is moving to Digital Product Release (DPR). Currently, each change request associated with a release generates its own approvers based on the change approval policies. For example, a release with 10 change requests may have 10 separate sets of approvers. We want to manage approvals centrally at the release level instead. Does either the deprecated RM Release plugin or the current DPR plugin support a release-centric approval framework?
1 release --- 10 change request -- 1) separate approvals -------------------->
2)separate approvals -------------------->
3)separate approvals --------------->
based on change approval policies -- so we want here release based approval policies at release level once we approve at release level it should not ask at individual change is that possible at DPR or releasev2 plugin
