Mercurial > evolve
changeset 5423:ba213f62fd50
readme: improve the extension purpose section
| author | Anton Shestakov <av6@dwimlabs.net> |
|---|---|
| date | Fri, 17 Jul 2020 09:56:22 +0800 |
| parents | 39cd95b6f566 |
| children | ca76e63e76dc |
| files | README.rst |
| diffstat | 1 files changed, 9 insertions(+), 9 deletions(-) [+] |
line wrap: on
line diff
--- a/README.rst Fri Jul 17 09:52:37 2020 +0800 +++ b/README.rst Fri Jul 17 09:56:22 2020 +0800 @@ -93,18 +93,18 @@ ================= The goal of this extension is to provide an appropriate place for code and -concept related to changeset evolution to mature. In this extension we allow -for hackier code, unlocking quick experimentation and faster iterations. +concepts related to `changeset evolution`_ to mature. In this extension we +allow hackier code, unlocking quick experimentation and faster iterations. -In addition, the evolve extensions support a wider set of Mercurial version, -allowing us to reach a larger user base for feedback. The Evolve extension is -not tight to the Mercurial release cycle and can release new feature and bug -fix at a higher rate if necessary. +In addition, evolve extension supports a wide range of Mercurial versions, +allowing us to reach a larger user base for feedback. The extension is not tied +to the Mercurial release cycle and can release new features and bug fixes at a +higher rate if necessary. -Once a concept is ready enough, its implementation is moved into Mercurial -core. The maturation period helped us to get a clearer picture of what was +Once a concept is deemed ready, its implementation is moved into core +Mercurial. The maturation period helped us to get a clearer picture of what was needed. During the upstreaming process, we can use this clearer picture to -clean up the code and upgrade it to an appropriate quality for Mercurial core. +clean up the code and upgrade it to an appropriate quality for core Mercurial. Python 3 Support ================