> We could not call it 1.100 because it would break the old automatic
> upgrade mechanism (1 comes before 9, yikes).
>
Why not make the upgrade from old version a two-step process?  Or is
this too high a price to pay for being absolutely clear that the API
not been broken?

I know bumping major versions is all the rage, but isn't backward
compatibility one of the strongest selling points of web2py?

Reply via email to