comparison README @ 5194:f478ac0a818f

readme: copywrite the section about branch policy, wrap long lines
author Anton Shestakov <av6@dwimlabs.net>
date Wed, 11 Mar 2020 15:55:36 +0700
parents b8b234123fe6
children 85640f1feced
comparison
equal deleted inserted replaced
5193:a4d081923c81 5194:f478ac0a818f
140 $ python $HGSRC/tests/run-tests.py 140 $ python $HGSRC/tests/run-tests.py
141 141
142 Branch policy 142 Branch policy
143 ------------- 143 -------------
144 144
145 The evolve test are highly impacted by changes in core. To deal with this, we use named branches. 145 The evolve tests are highly impacted by changes in core. To deal with this, we
146 146 use named branches.
147 There are two main branches: "stable" and "default". Tests on these branch are 147
148 supposed to pass with the corresponding "default" and "stable" branch from core 148 There are two main branches: "stable" and "default". Tests on these branches
149 Mercurial. The documentation is built from the tip of stable. 149 are supposed to pass with the corresponding "default" and "stable" branch from
150 150 core Mercurial. The documentation is built from the tip of stable.
151 In addition, we have compatibility branches to check tests on older version of 151
152 In addition, we have compatibility branches to check tests on older versions of
152 Mercurial. They are the "mercurial-x.y" branches. They are used to apply 153 Mercurial. They are the "mercurial-x.y" branches. They are used to apply
153 expected test change only, no code change should happen there. 154 expected test changes only, no code changes should happen there.
154 155
155 test output change from a changeset in core should adds the following line to their description: 156 Test output changes from a changeset in core should add the following line to
157 their patch description:
156 158
157 CORE-TEST-OUTPUT-UPDATE: <CORE-NODE-ID> 159 CORE-TEST-OUTPUT-UPDATE: <CORE-NODE-ID>
158 160
159 161
160 Format-source config 162 Format-source config