comparison docs/index.rst @ 2882:4b7252600e57

doc-front-pagE: add a paragraph about "why the extension" Let us clarify why there is an extension in the first place.
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Wed, 30 Aug 2017 11:25:51 +0200
parents 9b270ce3763b
children a23045b61e6d
comparison
equal deleted inserted replaced
2881:9b270ce3763b 2882:4b7252600e57
117 * Explore and audit the rewrite history of a changeset. Since Mercurial is 117 * Explore and audit the rewrite history of a changeset. Since Mercurial is
118 tracking the edition you make to a changeset, you can look at the history of 118 tracking the edition you make to a changeset, you can look at the history of
119 these editions. This is similar to Mercurial tracking the history of a file 119 these editions. This is similar to Mercurial tracking the history of a file
120 edition, but at the changeset level. 120 edition, but at the changeset level.
121 121
122 Why the `evolve` extension
123 --------------------------
124
125 Mercurial core already has some support for changeset evolution so why have a
126 dedicated extension?
127
128 The long-term plan for ``evolve`` is to add it to core Mercurial. However,
129 having the extension helps us experimenting with various user experience
130 approaches and technical prototype. Having a dedicated extensions help current
131 user to deploy the later changes quickly and provides the developers with
132 low latency feedbacks.
133
134 Whenever we are happy with a direction experimented in the extension, the
135 relevant code go upstream.
136
122 ``evolve`` is experimental! 137 ``evolve`` is experimental!
123 --------------------------- 138 ---------------------------
124 139
125 The long-term plan for ``evolve`` is to add it to core Mercurial. 140 The long-term plan for ``evolve`` is to add it to core Mercurial.
126 However, it is not yet stable enough for that. In particular: 141 However, it is not yet stable enough for that. In particular: