Evolve & Tagging

[Sebastian Unger]

OK now I finally got around to reading the write-up Pierre linked to. Of
all the solutions listed, the only ones that strike me as valid and
suitable are 3.5.4 (turn public on tag) and 3.5.5 (turn tagged public on
push). Regarding their cons:

> loose the ability to fix tagging error before publishing,
Why? Fixing a tag issue is a manual operation in any case. One can just
strip the tag and change the phase manually.

> break backward compatibility,
I don't see how changing the phase will break anything? Amending a change
set after tagging it was always a broken workflow since it leaves the tag
dangling. So preventing this sequence would simply make things safer.

> hard to revert if we get something better,
How would it be hard to revert? You'd just stop changing it to public.

That 3.5.5 does not handle the local case is a real drawback. I think 3.5.4
is better for that reason.

Cheers,
Seb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160511/4b11d0bc/attachment-0002.html>