Evolve & Tagging
David Douard
david.douard at logilab.fr
Wed May 11 09:36:17 UTC 2016
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...
> Cheers,
> Seb
>
--
David DOUARD LOGILAB
Directeur du département Outils & Systèmes
+33 1 45 32 03 12 david.douard at logilab.fr
http://www.logilab.fr/id/david.douard
Formations - http://www.logilab.fr/formations
Développements - http://www.logilab.fr/services
Gestion de connaissances - http://www.cubicweb.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: david_douard.vcf
Type: text/x-vcard
Size: 302 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160511/d030a1d6/attachment-0002.vcf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160511/d030a1d6/attachment.asc>
More information about the Evolve-testers
mailing list