[PATCH 3 of 3] dispatch: only check compatibility against major and minor versions
Augie Fackler
raf at durin42.com
Fri Jan 16 10:09:28 CST 2015
On Fri, Jan 16, 2015 at 12:06:41AM -0800, Pierre-Yves David wrote:
>
>
> 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).
This appears to be the exception rather than the rule - we typically
only do prep work in hg-git and hgsubversion for the major releases,
and assume we're good for the next few months.
>
> But I kind of agree that updating for each version is too tedious to ever
> happen (I do not do it).
Yup.
>
> I'll let the nigh rest over it.
I'm going to queue these.
>
> --
> Pierre-Yves David
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
More information about the Mercurial-devel
mailing list