current state of evolve vs core in 3.7.3
Matt Mackall
mpm at selenic.com
Tue Jun 28 19:58:12 UTC 2016
On Tue, 2016-06-28 at 11:53 -0700, Lee Nave wrote:
> There are these warnings in the docs:
>
> "Using this EvolveExtension will alter some of the core commands and
> behaviors."
>
> "The evolve extension enables the ChangesetEvolution feature, changing some
> of Mercurial's default behavior.
>
> history rewriting commands do not strip changesets anymore; they make
> them obsolete.
> history rewriting commands will work on any changesets, possibly
> creating unstable changesets.
> pull and push exchange obsolescence data with other evolve-enabled
> repositories - this may have a performance impact!"
>
> We are upgrading our server from 2.7 to 3.7.3 and I'm wondering if these
> warnings still apply. It is not clear to me what in the evolve extension
> is not already in 3.7.3 core and if those things are not considered
> production-ready.
All of the warnings still apply.
Some of the mechanisms are in core, most of the ui is not. It is certainly
possible for individual developers ("power users") to use evolve locally in just
about any development environment (for instance, there are many evolve users at
Facebook), but it's still fragile enough that I wouldn't yet make it a mandatory
part of the workflow/infrastructure for any team of more than a handful of
people.
--
Mathematics is the supreme nostalgia of our time.
More information about the Evolve-testers
mailing list