Evolve & Tagging
Sébastien Gautrin
sebastien.gautrin at gmail.com
Tue May 10 12:38:18 UTC 2016
On 10/05/16 14:11, Pierre-Yves David wrote:
> On 05/10/2016 12:46 PM, Sebastian Unger wrote:
>> Hi,
>>
>> Just an observation: The tag command should probably refuse to tag a
>> non-public changeset. This isn't strictly evolve related, but it only
>> becomes a big issue with evolve work flows.
>
> Tagging + draft is clearly an issue, however the correct approach to
> take is unclear and the problem still need to be tackled. There is
> multiple ideas flying around. I've written a short summary of them on
> the wiki:
>
> https://www.mercurial-scm.org/wiki/ChangesetEvolutionDevel#Tagging_draft_changeset
>
>
> Cheers
>
With regards to the con you mentionned for this option in the wiki
> * massive backward compatibility breakage, sensible user script will
> break,
>
I can attest that it would be really problematic in our environment,
using the release plugin with maven, which does three draft commits (it
can push the changes afterwards, but that would not change the problem):
updating project version for the release version, adding a tag, updating
project version to next snapshot. Maven is wildly used in the java
world, and similar breakage would affect other build systems (either
public or custom).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160510/6b0c5427/attachment-0002.html>
More information about the Evolve-testers
mailing list