Here are my observations after standing up Oracle EPM 188.8.131.52:
- The install and config steps in 184.108.40.206 are identical to 220.127.116.11 in all respects. You still need to worry about RCU, OHS still isn't its own Windows service, etc.
- The Oracle Middleware layer is also identical between 18.104.22.168 and 22.214.171.124, with the exception of 2 patches that 126.96.36.199 automatically installs: 27747932 and 27430060. Simply applying these 2 patches to an 188.8.131.52 system doesn't give it the Edge & Chrome certifications; you need to be on 184.108.40.206 as Oracle recompiled a lot of their Java classes within the EPM 220.127.116.11 .ear files for Workspace, Planning, etc. We can see evidence of this when we crawl through the .war files within the .ear files in a tool such as 7-zip.
- As with 18.104.22.168, you'll find 22.214.171.124 is one year behind (as of this writing) in terms of the quarterly Oracle Critical Patch Updates for WebLogic, Java, and OHS.
- There is no need to install 126.96.36.199 first and then in-place upgrade to 188.8.131.52. You may install 184.108.40.206 fresh and then LCM your application content from 220.127.116.11.
IE11 will continue to receive Microsoft security updates for as long as Windows 10 remains supported, but as they say, "shots have been fired". As Microsoft has indicated Edge is the browser of the future, so has Oracle and thus (I suspect) the push to get 18.104.22.168 out the door. (People have been clamoring for Chrome certification as well)
Further reading on Microsoft's site: Microsoft Lifecycle FAQ