Skip to content
This repository was archived by the owner on Oct 17, 2022. It is now read-only.

Conversation

@nickva
Copy link
Contributor

@nickva nickva commented Feb 29, 2016

JIRA: COUCHDB-2954

@kxepal
Copy link
Member

kxepal commented Feb 29, 2016

I only now get caught by "deprecate" word: imho, better to use "Drop" or "Remove" here since deprecation in classic workflow assumes that feature exists, but soon will be removed. Here we actually remove it completely without deprecation phase (which eventually will happen on 1.x.x branch).

So same +1 for me, but if you update the wording then +100 (:

@nickva nickva force-pushed the couchdb-2954-deprecate-replicator-db branch from 0f571e4 to 3a527ba Compare February 29, 2016 18:36
@nickva nickva changed the title Deprecate configurable replicator db name Remove configurable replicator db name functionality Feb 29, 2016
@nickva
Copy link
Contributor Author

nickva commented Feb 29, 2016

Agreed. Makes sense. Updated to "Remove"

It was replaced with the ability to have multiple replicator
databases in 2.0

JIRA: COUCHDB-2954
@nickva nickva force-pushed the couchdb-2954-deprecate-replicator-db branch from 3a527ba to ec3cc22 Compare February 29, 2016 18:38
@asfgit asfgit merged commit ec3cc22 into apache:master Mar 2, 2016
asfgit pushed a commit that referenced this pull request Mar 2, 2016
    - #41

    This closes #41

    Signed-off-by: ILYA Khlopotov <iilyak@ca.ibm.com>
nickva pushed a commit to nickva/couchdb that referenced this pull request Sep 7, 2022
    - apache/couchdb-documentation#41

    This closes apache#41

    Signed-off-by: ILYA Khlopotov <iilyak@ca.ibm.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants