Difficulties with permanence of obsolete markers
Scott Bilas
scobi at unity3d.com
Tue Aug 2 12:52:37 UTC 2016
>
> > Am I misunderstanding anything about evolve here? Any guidance on how we
> > can improve our workflow?
>
> Something that emerged from evolve beta testing is that there is things
> you "can edit" (draft) but probably should not (eg: other people
> changesets, things currently in review). We'll likely grow some
> mechanism to warn the user about probably harmful action, requiring
> extra confirmation for the operation.
>
Yes, I find myself wanting a special phase for "published draft". :)
> Something quite similar currently in the making is the detection of edit
> that will create divergence, preventing user to shoot themselves in the
> foot by default. For there will likely expand the logic to fit more
> case. Eventually this should help your usecase more definitely.
>
Very happy to hear.
> I hope this message helped you getting a grasp of how much of your
> struggle is by design and how much is by partial implementation.
>
Yes, this was very helpful, thank you.
Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/evolve-testers/attachments/20160802/67123577/attachment.html>
More information about the Evolve-testers
mailing list