[ 
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834602#comment-13834602
 ] 

Benoit Chesneau commented on COUCHDB-1934:
------------------------------------------

Imo we shouldn't simply remove it from our repository. Lot of html5 apps around 
are using it from `_utils/` , simply changing it means that on next upgrade 
everyone will have to replace it by ...what... Another link? 

It will be probably a change that some people will do. Then what? Who will 
maintain this code? Should we consider it as abandonware? 

Does it also mean that people will have to use backbone by default? Then maybe 
we should document it ?

I have no clear answers on that topic but imo:

- if we remove it from our code we should probably do it in 2 steps:
   1. annonce it will be deprecated in next version and removed in n+2
   2. start to put in in a repo, move the tickets to it, and askk for a 
maintainer
- document how to build an HTML5 apps embedded in couchdb without it

Thoughts?

> 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)

Reply via email to