Ah. We disagree on this one. Removing couch.jquery.js seems minor enough that we'd hold off. But changing the way document meta data works is a prime candidate for bumping our major point version.
Semver is meant to encourage and enable these sorts of changes, and we should take full advantage of it. If we agree on a change here, and it is ready to ship, we should ship it. End of story. :) And yep, that will mean bumping to 2.0, and that's fine. And we'll keep the 1.0 line around for 12 months and backport things to it. (I believe that's the policy.) On 4 December 2013 13:34, Alexander Shorin <[email protected]> wrote: > On Wed, Dec 4, 2013 at 4:00 PM, Noah Slater <[email protected]> wrote: >> On 3 December 2013 15:01, Benjamin Young <[email protected]> wrote: >>> I realize these are extreme API shifts, and would need to wait for CouchDB >>> 2.0. >> >> No need to wait for anything. We could land this as soon as it is >> ready, and then the next release becomes 2.0. That's the flexibility >> our new release process gives us. > > I think Benjamin is about "to not produce too much releases with > broken backward compatibility" - that will be hard to support and only > confuse users regardless how flexible is our release process (: > > -- > ,,,^..^,,, -- Noah Slater https://twitter.com/nslater
