The various updates for Windows 10 should have tag synonyms for their official titles.

This assumes that every feature update will also have a release name associated with it. There are already exceptions to the "feature update" has a name rule. The exception of course being the build released back in July 2015. It is also true that in that case, it also does not have a version notation (i.e. v1703, v1607, v1511).

I suggest, we make the tags synonyms of one another, only if, additional tags are created for that release. I also suggest the primary tag notation should be that of the release date notation (i.e. v1703, v1607, v1511).

If and when, additional tags are created for a major feature release, we can link the synonym link at that point.

The various updates for Windows 10 should have tag synonyms for their official titles.

This assumes that every feature update will also have a release name associated with it. There are already exceptions to the "feature update" has a name rule. The exception of course being the build released back in July 2015. It is also true that in that case, it also does not have a version notation, i.e. v1703, v1607, v1511

I suggest, we make the tags synonyms of one another, only if, additional tags are created for that release. I also suggest the primary tag notation should be that of the release date notation (i.e. v1703, v1607, v1511).

If and when, additional tags are created for a major feature release, we can link the synonym link at that point.