Lets make Minerva a true skin, and separate it from the other features MF has (Nearby, etc.). I'm guessing this is going to be difficult, but I have no clue :)
= Minerva or MinervaNeue
Renaming the skin to MinervaNeue is problematic as it will require updates to existing extensions and configs to ensure they take into account both Minerva and Minerva-Neue. A benefit of doing this however is that sysadmins can install MinervaNeue skin alongside Minerva before upgrading MobileFrontend.
= Preparation steps
[] Setup CI on Minerva repository (merge pending)
[x] Setup browser tests for Minerva repository
[x] Setup translations on the new Minerva repository
[] Deploy Minerva to the cluster as a dormant repository
= The big switcheroo
[] Transfer code from MobileFrontend to Minerva
[] To begin with, Minerva will depend on MobileFrontend
[] If Minerva is installed without MobileFrontend an exception will be thrown
[] If MobileFrontend is installed without Minerva an error will be logged using LoggerFactory saying that no mobile skin has been setup
[] Browser tests will move from MobileFrontend to Minerva, so ensure there is no disruption to browser test jobs
= Sign off checklist
[] Create a new epic for removing the MobileFrontend dependency on Minerva
Related: T72142