<br><br>On Monday 22 August 2016, Roland Haas <<a href="mailto:rhaas@illinois.edu">rhaas@illinois.edu</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all,<br>
<br>
> Tags also cannot be moved; that is the point - they always point to<br>
> the same version.<br>
I agree, they *shouldn't* be moved and are not designed to be. You can<br>
however delete and re-create them, which would be sufficient for our<br>
purpose since all we want is a single name that can move along with the<br>
releases.<br>
</blockquote><div><br></div><div>Tags are really not designed with this in mind, so weird things can and do happen if you do this sort of thing.</div><div><br></div><div>There are robust solutions to this generic issue. They usually revolve around a particular workflow. The most popular one is git-flow; see e.g. <a href="https://www.atlassian.com/git/tutorials/comparing-workflows">https://www.atlassian.com/git/tutorials/comparing-workflows</a> for a good overview.</div><div><br></div><div>I'm not necessarily advocating that th ET change workflow<span></span>, but it could be worth considering.</div><div><br></div><div>Barry</div>