equal
deleted
inserted
replaced
77 |
77 |
78 $ hg config --edit # adds the two line below: |
78 $ hg config --edit # adds the two line below: |
79 [extensions] |
79 [extensions] |
80 evolve.serveronly = |
80 evolve.serveronly = |
81 |
81 |
|
82 Extension Purpose |
|
83 ================= |
|
84 |
|
85 The goal of this extension is to provide an appropriate place for code and |
|
86 concept related to changeset evolution to mature. In this extension we allow |
|
87 for hackier code, unlocking quick experimentation and faster iterations. |
|
88 |
|
89 In addition, the evolve extensions support a wider set of Mercurial version, |
|
90 allowing us to reach a larger user base for feedback. The Evolve extension is |
|
91 not tight to the Mercurial release cycle and can release new feature and bug |
|
92 fix at a higher rate if necessary. |
|
93 |
|
94 Once a concept is ready enough, its implementation is moved into Mercurial |
|
95 core. The maturation period helped us to get a clearer picture of what was |
|
96 needed. During the upstreaming process, we can use this clearer picture to |
|
97 clean up the code and upgrade it to an appropriate quality for Mercurial core. |
82 |
98 |
83 How to Contribute |
99 How to Contribute |
84 ================= |
100 ================= |
85 |
101 |
86 Discussion happens on the #hg-evolve IRC on freenode_. |
102 Discussion happens on the #hg-evolve IRC on freenode_. |
123 Mercurial. The documentation is built from the tip of stable. |
139 Mercurial. The documentation is built from the tip of stable. |
124 |
140 |
125 In addition, we have compatibility branches to check tests on older version of |
141 In addition, we have compatibility branches to check tests on older version of |
126 Mercurial. They are the "mercurial-x.y" branches. They are used to apply |
142 Mercurial. They are the "mercurial-x.y" branches. They are used to apply |
127 expected test change only, no code change should happen there. |
143 expected test change only, no code change should happen there. |
|
144 |
|
145 test output change from a changeset in core should adds the following line to their description: |
|
146 |
|
147 CORE-TEST-OUTPUT-UPDATE: <CORE-NODE-ID> |