v2017.2.0.1-Stabilization?
I thought we were dropping the v prefix on the releases?
Also, shouldn't it be 2017.2.1.0 as it'll most likely reflect the new release Unity will have by the time we approve it?
I copied the tag from your release draft. Certainly that can change between now and then.
If a new Unity release happens, we can address that. The branch name doesn't lock us into a tag.
I mistakenly kept the v this time, but, again, the branch name doesn't lock us into a release tag.
No worries, just asking.
All good! I wanted to try to explain my thought process as thoroughly as possible.