I think the version discussion boils down to utility vs complexity (specifically the complexity to understand and communicate how to use the map.yml version field).
There is a discussion open in github issues whether to bake categories into map.yml which would put it under map maker control and alleviate the map admin team from an ongoing upkeep task.
Deployment wise, remaining we'll need to generate a map.yml for every repo and upload it presumably to the top-most directory of each map. FWIW this should be not that bad, currently the map engine is now rigged to generate a map.yml file for any downloaded maps that do not have it, we'd only need to take the generated file and upload it.
Otherwise, does the current map.yml look good and is it clear? The XML path I think is maybe the most error prone and it's the path of any game XML relative to the map.yml file. If the map.yml file is at the top level of a map (expected), then the XML path is really just the path to the XML file from the map folder..
Last, hopefully it's also well understood that game and map name will now come from the map.yml file and the corresponding XML attributes would be considered deprecated and no longer read by 2.6+ engines.
The map.yml also removes the need for a map repository or map zip to have any kind of specific naming to match the map name in the XML, the map repo and zip could have any reasonable name and would essentially no longer matter.


