Align new 9.1.1 XM images with existing ones

[sshushliapin]

Thank you for adding 9.1.1 support! From the recent release notes:

[Added] Sitecore 9.1.1 XM and XP on ltsc2019/1809, please notice that the xm1 tags is now just xm

Is there any reason for this? Does it make sense to align the naming conventions and rename all the existing xm1 images into xm (or vice versa)?

Currently I'm using docker hub with 20 repositories ($22/month) to build 9.x images. 9.1.1 introduces 3 new xm repos that do not feet my plan and force me to either switch to the next one ($50) or to configure local registry (which I'd like to avoid).

Please let me know if I should come up with a PR fixing this.

[pbering]

I'm sorry that I didn't foresee the consequences of this rename for those of you using the "pay per repository" model!

I think that it would be best to go back to using xm1 instead of changing all the other to xm. The reason why I chose xm1 to begin with was to reflect which package it came from and that is also why xp is only xp since it's a mix of both xp0 and xp1 :)

What do you say?

[sshushliapin]

The reason why I chose xm1 to begin with was to reflect which package it came from

+1. I'd change it to xm1