Description of problem:

We encountered a scenario in our release process that we need to watch out for going forward and we needed to immediately fix by release ACM 2.12.7 and MCE 2.7.8: * We started to publish 2.12.6 and MCE 2.7.7 but then found a hive problem so we did not complete publishing.  (bundles published but not the catalog)

• We shipped ACM 2.15.0
• We finally got the problem fixed for 2.12.6 and completed the publishing of that release.

Because of the ordering above customers actually could have ended up on the unpublished release in the first item above (with the hive issue).
To fix the situation, we did a quick new release - ACM 2.12.7 and MCE 2.7.8.
I don't think we had any new content in this release – it was just to make sure anyone that automatically moved to the MCE 2.7.7 release with the hive issue, got moved to MCE 2.7.8.

Another way of saying this: * ACM 2.15.0 publishing caused our MCE 2.7.7 with hive problem to be released without us realizing it.

• ACM 2.12.6 shipped and included an "updated" MCE 2.7.7 without the hive problem, but anyone that updated MCE already could have been on the problem version.
• ACM 2.12.7 was shipped only to drive another round of updates to make sure anyone that moved to MCE 2.7.7 would now be on MCE 2.7.8 and we wouldn't have to wonder if they did or didn't have the hive issue

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: