[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834739#comment-13834739
]
Robert Newson commented on COUCHDB-1934:
----------------------------------------
Is there a way to make such a deprecation marker visible to the users that call
it? My -1 on the mailing list was conditional on hearing "no good reasons to
remove it". But, since you've just made some, I'm fine with deprecation ahead
of removal, as long as we make some effort to communicate this. A major version
bump can do that (to coincide with fauxton replacing futon entirely, except for
preserving the unused jquery.couch.js file) but we should do more (tweet, user@
post, etc).
The major version bump will also need to be clearly described as folks will
assume it's the bigcouch merge. So, we should clarify our adoption of semver
semantics at that time.
> jquery.couch status
> -------------------
>
> Key: COUCHDB-1934
> URL: https://issues.apache.org/jira/browse/COUCHDB-1934
> Project: CouchDB
> Issue Type: Question
> Reporter: Alexander Shorin
>
> When [~nslater] had proposed to include [jquery.couch.js
> docs|http://daleharvey.github.io/jquery.couch.js-docs/symbols/] into official
> CouchDB one I recall old good time when we had discussed Futon.Next project.
> Suddenly, it was out of official mailing lists, so no references are
> available, but [~garren], [~dch], [~bigbluehat] and [~ryanramage] were there
> and our discussion was around jquery vs backbone vs pouchdb. Backbone won.
> Nowdays, we have Fauxton which doesn't used jquery.couch and based on
> Backbone. So it seems if we'll replace Futon with him this client library
> would be left orphan.
> So that's the question: what is the status of jquery.couch.js? Is it still
> actual and supported or going to be deprecated?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
