Re: [Monotone-devel] netsync flag day justifies bumping version number to 1.0

[Ludovic Brenta]

Selon Stephen Leake <address@hidden>:
> Thomas Keller <address@hidden> writes:
> 
> > So I think now that this change is in nvm, we should start dealing with
> > that. I see basically three options:
> >
> > a) We don't care at all about netsync breakage. After all there *is* a
> > reason why we have no 1 as major version number... If you find this
> > unfair towards bigger projects, ok, then lets make a 0.44.x branch and
> > split up the development here. If people want the new features, they
> > have to upgrade, if not, we promise that we fix critical bugs for the
> > 0.44.x line for at least the additional time we see projects using the
> > old client. Since this is a rather small community and monotone hasn't
> > seen many critical bugs in its history, I think this is managable.
> 
> This is a good fall back plan.

I second this; that's basically what I asked for in my first email, with the
only difference that 0.44.x should be 0.x and 0.45 should be 1.0. This makes
the incompatibility prominent and easy to warn about and to diagnose. This is
in addition to the benefit I already described with multiple versions in a
distribution.

-- 
Ludovic Brenta.