You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Adam Kocoloski <ko...@apache.org> on 2009/09/14 21:09:00 UTC
Re: svn commit: r814778 - in /couchdb/trunk: share/www/script/ share/www/script/test/ src/couchdb/
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. Best,
Adam
On Sep 14, 2009, at 3:03 PM, jchris@apache.org wrote:
> Author: jchris
> Date: Mon Sep 14 19:03:36 2009
> New Revision: 814778
>
> URL: http://svn.apache.org/viewvc?rev=814778&view=rev
> Log:
> removed _all_docs_by_seq in favor of _changes
Re: svn commit: r814778 - in /couchdb/trunk: share/www/script/ share/www/script/test/ src/couchdb/
Posted by Jan Lehnardt <ja...@apache.org>.
On 14 Sep 2009, at 21:44, Chris Anderson wrote:
> On Mon, Sep 14, 2009 at 12:23 PM, Adam Kocoloski
> <ko...@apache.org> wrote:
>> On Sep 14, 2009, at 3:12 PM, Chris Anderson wrote:
>>
>>> On Mon, Sep 14, 2009 at 12:09 PM, Adam Kocoloski <kocolosk@apache.org
>>> >
>>> 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"
>>
>> +1 from me.
>>
>
> This commit makes me want to release 0.10. Trunk has moved distinctly
> into 0.11 territory now, so people on the edge are gonna get another
> bumpy ride for a few weeks. 0.10 would solve this.
LET'S DO IT!
Noah, do you have time to prepare the release?
Cheers
Jan
--
Re: svn commit: r814778 - in /couchdb/trunk: share/www/script/
share/www/script/test/ src/couchdb/
Posted by Chris Anderson <jc...@apache.org>.
On Mon, Sep 14, 2009 at 12:23 PM, Adam Kocoloski <ko...@apache.org> wrote:
> On Sep 14, 2009, at 3:12 PM, Chris Anderson wrote:
>
>> On Mon, Sep 14, 2009 at 12:09 PM, Adam Kocoloski <ko...@apache.org>
>> 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"
>
> +1 from me.
>
This commit makes me want to release 0.10. Trunk has moved distinctly
into 0.11 territory now, so people on the edge are gonna get another
bumpy ride for a few weeks. 0.10 would solve this.
Chris
--
Chris Anderson
http://jchrisa.net
http://couch.io
Re: svn commit: r814778 - in /couchdb/trunk: share/www/script/ share/www/script/test/ src/couchdb/
Posted by Adam Kocoloski <ko...@apache.org>.
On Sep 14, 2009, at 3:12 PM, Chris Anderson wrote:
> On Mon, Sep 14, 2009 at 12:09 PM, Adam Kocoloski
> <ko...@apache.org> 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"
+1 from me.
Re: svn commit: r814778 - in /couchdb/trunk: share/www/script/
share/www/script/test/ src/couchdb/
Posted by Chris Anderson <jc...@apache.org>.
On Mon, Sep 14, 2009 at 2:04 PM, Paul Davis <pa...@gmail.com> wrote:
> On Mon, Sep 14, 2009 at 3:12 PM, Chris Anderson <jc...@apache.org> wrote:
>> On Mon, Sep 14, 2009 at 12:09 PM, Adam Kocoloski <ko...@apache.org> 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
Re: svn commit: r814778 - in /couchdb/trunk: share/www/script/
share/www/script/test/ src/couchdb/
Posted by Paul Davis <pa...@gmail.com>.
On Mon, Sep 14, 2009 at 3:12 PM, Chris Anderson <jc...@apache.org> wrote:
> On Mon, Sep 14, 2009 at 12:09 PM, Adam Kocoloski <ko...@apache.org> 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?
Re: svn commit: r814778 - in /couchdb/trunk: share/www/script/
share/www/script/test/ src/couchdb/
Posted by Chris Anderson <jc...@apache.org>.
On Mon, Sep 14, 2009 at 12:09 PM, Adam Kocoloski <ko...@apache.org> 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"
> Best,
>
> Adam
>
> On Sep 14, 2009, at 3:03 PM, jchris@apache.org wrote:
>
>> Author: jchris
>> Date: Mon Sep 14 19:03:36 2009
>> New Revision: 814778
>>
>> URL: http://svn.apache.org/viewvc?rev=814778&view=rev
>> Log:
>> removed _all_docs_by_seq in favor of _changes
>
>
--
Chris Anderson
http://jchrisa.net
http://couch.io