On Mon, Jan 9, 2012 at 1:57 PM, Chris Hostetter <[email protected]> wrote:
> once we make a 4x branch, the only hard line we *have* to stand behind is > not to make file format changes to 3x -- that doesn't mean there can't be > minor feature releases like 3.7, etc... (it's unlikely that there should > ever be a need for them, but there's no reason to forbid it -- just like > there's nothing stoping us from putting out a 2.10 release right now if > some previously silent but large user base of the 2.x APIs comes a long > clammoring for a backport of some small feature) > Well its not just file format changes, for example its also APIs. If 3.6 had an API that worked in a backwards compatible way with 4.0, but then we broke it in 3.7 and 4.1 or something, that would be way too confusing. Then a user upgrades to 3.6 and finds its hard to go from 3.6 to 4.0 (which they think is an upgrade, but for that API its in fact a downgrade). Setting 3.x to "bugfix-only" prevents these kinds things too... I still think its the only reasonable approach. -- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
