Again, I should understand the direction you ack here ... and its not clear in any way I try to read it
lets summaries current status:
master == v4.17.999 (I recalled 4.18 tag for 4.0... probably it hasn't happened yet)
ovit-3.6.3 last commit points to v4.17.23 (and also contains in its history 4.17.22 4.17.21 4.17.20 and 4.17.19
ovirt-3.6 == was not tagged since v4.17.19
So, as far as I see - last "official published" version is tagged anyway. once we'll finish with z-streams, we can continue tagging only on ovirt-3.6 branch. but as long as we publish new snapshots (or z-stream releases as I call them) we can continue the tagging only on ovirt-3.6.3 branch
The rest of your suggestions can't help in any way. if you prefer you can use 4th level versioning (4.17.x-y) later on. but currently we just continue to raise the current 4.17 we have
now, getting back to the origin mail that Sandro sent:
""" snip
this is correct - no problem with that approach, new tag still will be higher then 4.17.19 as we see with 4.17.23
> This make impossible to upgrade from stable (4.17.23) to latest snapshot.
But we just said that stable (ovirt-3.6) is 4.17.19 and latest is 4.17.23 - so it sounds right to me.
> This also break dependencies on other projects requiring the latest released version like hosted engine.
No its not. HE may require 4.17.23 which is the latest we publish as part of 3.6.3
"""
Yaniv Bronhaim.