Evolve & Tagging

[Sean Farley]

Sebastian Unger <sebunger44 at gmail.com> writes:

> On May 11, 2016 12:45 AM, "Sébastien Gautrin" <sebastien.gautrin at gmail.com>
> wrote:
>> Considering the purpose of evolve, the “natural” expectation would be
> that after evolving the code base the affected tag point to the replacement
> target (option 3.5.1 in the list).
>
> I strongly disagree here! A tag is supposed to mark a particular state of
> the code base for instance associated with a release. That state must be
> immutable.
>
> Why not simply make the tagged change sets public as part of the tag
> command? That should not affect any workflows out there and would achieve
> making the target of the tag immutable.

Yes, this is being contemplated heavily. I tentatively agree with this
but a longer discussion will need to be had for sure.