Evolve & Tagging

Ingo von Borstel newsgroups at planetmaker.de
Wed May 11 10:55:43 UTC 2016


On 11.05.2016 11:36, David Douard wrote:
> On 05/10/2016 09:16 PM, Sebastian Unger wrote:
>>
>> On May 11, 2016 12:45 AM, "Sébastien Gautrin" <sebastien.gautrin at gmail.com <mailto: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.
> 
> 
> I am very not found of this solution. It's a major UX flow IMHO (unexpected change of state) that will make people 
> publish changesets by mistake even more than what happen now...

Let me chime in: Publishing a tag automatically would be pretty bad
design IMHO. I sometimes locally tag builds and run as local test a
release build of that tag before I push. I would be annoyed if that
changed the phase of those commits. I rely on changesets becoming public
only when I push draft ones or mark them as public explicitly.

Cheers
planetmaker
> 
>  
>> Cheers,
>> Seb
>>
> 
> 
> 
> 
> _______________________________________________
> Evolve-testers mailing list
> Evolve-testers at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/evolve-testers
> 




More information about the Evolve-testers mailing list