[PATCH 3 of 3] dispatch: only check compatibility against major and minor versions
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Fri Jan 16 02:06:41 CST 2015
On 01/15/2015 10:52 PM, Ryan McElroy wrote:
> I'm happy enough with this series (I'm not for or against this third
> patch the the other two seem strictly positive).
I've pushed the two first on the clowncopter
> I might argue against
> this third patch on the basis that major revisions don't seem to have
> any semantic meaning in mercurial (as I understand it -- but I'm new
> here -- hg goes from 2.9 to 3.0 on a schedule, not on a set of
> features). However, I could argue for it in that it reduces the overhead
> of maintaining extensions to every ten freezes instead of every freeze,
> which is probably a net win for the world overall.
I think you are getting this wrong. The changes move from declaring
compatibility from "1.9.3" to "1.9".
I'm not sure what I think about it. I certainly already did change that
break BC between bug fixe release (when bug is super bad).
But I kind of agree that updating for each version is too tedious to
ever happen (I do not do it).
I'll let the nigh rest over it.
--
Pierre-Yves David
More information about the Mercurial-devel
mailing list