I'm putting this task in FIS 2.0 patches because this should be done in FIS 2.0 as support exception for some customers.
Changing the EAP productization process to publish those artifacts to MRRC seems complicated. Darren can you follow up with the EAP prod team to find the best way to publish those artifact to MRRC?
It can be that us publish them, but we need e.g. a way to be notified when a new version is available.