On Mon, Sep 14, 2009 at 2:04 PM, Paul Davis <[email protected]> wrote: > On Mon, Sep 14, 2009 at 3:12 PM, Chris Anderson <[email protected]> wrote: >> On Mon, Sep 14, 2009 at 12:09 PM, Adam Kocoloski <[email protected]> wrote: >>> Hi devs, I'm all for this commit, but what should we do about our 0.10 >>> "beta" release? If our next release doesn't have _all_docs_by_seq I think >>> the beta should deprecate or remove it. >> >> I think the plan is to leave both features in 0.10, with a deprecation >> warning on all_docs_by_seq, but I'm open to whatever. >> >> Also, I don't know what a deprecation warning would look like. maybe >> just a tag at the top of the response saying: >> "notice":"_all_docs_by_seq is deprecated, please use _changes" >> > > There's actually a HTTP Warning header that I've always wanted to use. > This could fit there. Though that begs the question, how many people > actually look at HTTP headers they're not expecting? >
Hehe, I'd love to see this, it actually looked like the only simple implementation of a deprecation (the make_view_fold_fun isn't very amenable to adding a message) - I was resigned to just sticking it in the docs and the code. Chris -- Chris Anderson http://jchrisa.net http://couch.io
