On Wed, Nov 27, 2013 at 4:05 PM, Robert Newson <[email protected]> wrote: > It's the other way around. If the next release removes jquery.couch.js > then it gets called 2.0.0. It doesn't imply we wait for "2.0". The > version *only* conveys compatibility, that's the semver way.
I was about that there is no reason to bump major version just because we decide to remove some javascript library that doesn't change the behaviour of the main project. It will be a bit awkward to read release notes for CouchDB 2.0 where nothing changed, but builtin javascript client based on some thirdparty framework was removed. Semver is semver, but it should be used wisely. > On 27 November 2013 12:01, Alexander Shorin <[email protected]> wrote: >> On Wed, Nov 27, 2013 at 3:48 PM, Robert Newson <[email protected]> wrote: >>> A major version bump (not to mention, a discussion) is needed if we're >>> to remove a long-standing component like jquery.couch.js. For my part, >>> I'm -1 on removing it having heard no good reason for doing so. >> >> Agreed with this. So the only chance to make it is the 2.0 release. >> Otherwise we have to continue support inside CouchDB project. >> >> -- >> ,,,^..^,,,
