important information about coming evolve 6.3.0: update client and server together

Pierre-Yves David pierre-yves.david at ens-lyon.org
Tue May 30 23:23:54 UTC 2017


TL;DR; 6.3.0 will fix a bug effecting obsmarkers discovery, upgrade 
client and server at the same time Otherwise push and pull will take 
more time and more bandwidth.

Hello evolve testers,

We just fixed a small bug in mercurial core affecting the computation of 
what obsolescence markers need to be synchronized alongside a group of 
changesets[1]. That will affect the various hashes that the obsmarkers 
discovery uses to perform its duty. This fix is backported to older 
version of Mercurial in the next version of the evolve extensions (to be 
released soon).

As a result, people exchanging obsolescence markers over the wire are 
recommended to upgrade all their evolve extension installs to 6.3.0 at 
the same time (client and server alike). Otherwise obsmarkers discovery 
might fails to detect common set of changeset when client and server 
uses different versions of the algorithm.This means the discovery 
process would make more round-trip that usual to detect less common 
markers than intended. Mercurial then send more obsolescence markers 
already known on the receiving side.

We are sorry to not provide a smoother update story. The logic fixed in 
core mercurial is in a function deep into the call stack so providing 
compatibility is non trivial here. As we are generally short in manpower 
we prefer to focus our energy on improving other aspect of evolve. If 
this upgrade prove challenging to you, please reply to this email with 
details about your setup and we'll see how we can help.

Cheers,

-- 
Pierre-Yves David

[1] https://www.mercurial-scm.org/repo/hg/rev/176d1a0ce385


More information about the Evolve-testers mailing list