Mercurial > evolve

comparison README @ 2537:4a467331ec79 stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
readme: clarify the branch policy
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Thu, 01 Jun 2017 02:28:36 +0200
parents 6da4ca7b3e4f
children 2b2addb23e96
comparison
equal deleted inserted replaced
2536:4c07dfedba32 2537:4a467331ec79
103 say in $HGSRC:: 103 say in $HGSRC::
104 104
105 $ cd tests 105 $ cd tests
106 $ python $HGSRC/tests/run-tests.py 106 $ python $HGSRC/tests/run-tests.py
107 107
108 (evolve's stable and default branches correspond to Mercurial's stable 108 Branch policy
109 and default branches. So to test evolve from default, you need 109 -------------
110 Mercurial on default.), Older version of Mercurial are supportd on their respective ``mercurial-x.y`` branches. 110
111 The evolve test are highly impacted by changes in core. To deal with this, we use named branches.
112
113 There are two main branches: "stable" and "default". Tests on these branch are
114 supposed to pass with the corresponding "default" and "stable" branch from core
115 Mercurial.
116
117 In addition, we have compatibility branches to check tests on older version of
118 Mercurial. They are the "mercurial-x.y" branches. They are used to apply
119 expected test change only, no code change should happen there.
111 120
112 Changelog 121 Changelog
113 ========= 122 =========
114 123
115 6.3.0 -- 2017-05-31 124 6.3.0 -- 2017-05-31