I'm also -1 on removing it. If we really plan to remove it we should do it gracefully. Add a big note somewhere, maybe even in the header of the source file notifying users that it will be deprecated.
Maybe even add a console.info or console.warn stating that it is a deprecated library. That way people have time to react to it. If we'd just remove it now because we know it is not used internally we might risk a bad image by breaking peoples applications. On Wed, Nov 27, 2013 at 1:51 PM, Robert Newson <[email protected]> wrote: > "where nothing changed," > > Removing jquery.couch.js will *break* some users. Neither of us know > how many users that is, or which users it is. The major version bump > is necessary to communicate this ("MAJOR version when you make > incompatible API changes"). We can deprecate it without needing to > bump the major, if that's our decision. > > A big part of semver is to stop being so precious about version > numbers. It codifies rules for version numbers for the sole intention > of conveying compatibility. You know that if your code works against > X.0.0 then it ill also work against X.1.0 and X.0.1. For example, if > the bigcouch merge didn't change API then we would not bump the major > for it (but we would bump the minor). > > B. > > On 27 November 2013 12:39, Alexander Shorin <[email protected]> wrote: > > On Wed, Nov 27, 2013 at 4:06 PM, Simon Metson <[email protected]> > wrote: > >> If the library is getting taken out to be maintained in an external > repo why not just maintain it in the asf one? The reason for deprecating it > would be to be honest that it’s not maintained code, if someone is > maintaining it then great, keep it in! > >> > >> That it’s not used by fauxton is immaterial imho. > > > > There are some thoughts about in the related ticket: > > https://issues.apache.org/jira/browse/COUCHDB-1934 > > > > Deprecated means that it becomes excluded from the CouchDB project. > > Probably, the word "deprecated" isn't correct one for this case. > > > > Personally, I have nothing against jquery.couch and if it will left in > > main repo it will be fine. But if no part of the project will use it > > (after fauxton stable release), it's reasonable to ask what it does > > in the source tree and wouldn't it be better to move it outside of it? > > That's all the talks (: > > > > -- > > ,,,^..^,,, > -- Octavian Damiean GitHub: https://github.com/mainerror
