Mercurial > evolve
changeset 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 |
files | docs/index.rst |
diffstat | 1 files changed, 15 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/index.rst Wed Aug 30 11:25:27 2017 +0200 +++ b/docs/index.rst Wed Aug 30 11:25:51 2017 +0200 @@ -119,6 +119,21 @@ these editions. This is similar to Mercurial tracking the history of a file edition, but at the changeset level. +Why the `evolve` extension +-------------------------- + +Mercurial core already has some support for changeset evolution so why have a +dedicated extension? + +The long-term plan for ``evolve`` is to add it to core Mercurial. However, +having the extension helps us experimenting with various user experience +approaches and technical prototype. Having a dedicated extensions help current +user to deploy the later changes quickly and provides the developers with +low latency feedbacks. + +Whenever we are happy with a direction experimented in the extension, the +relevant code go upstream. + ``evolve`` is experimental! ---------------------------