Github user rnewson commented on the issue:
https://github.com/apache/couchdb-couch-replicator/pull/47
Committers to couchdb should be focused on making 2.0 happen. If they want
to do other, unrelated work, they can keep it elsewhere for now.
---
If your project is set up for it,
Github user kxepal commented on the issue:
https://github.com/apache/couchdb-couch-replicator/pull/47
@rnewson Why not to create a branch for 2.0 and prepare release from there
while people still can work on new features and master? Sounds like gitflow-ish.
---
If your project is
Github user rnewson commented on the issue:
https://github.com/apache/couchdb-couch-replicator/pull/47
please remember that couchdb is frozen for the 2.0 release, please stop
merging new features or fixing that aren't 2.0 blockers.
@nickva @eiri @iilyak
---
If your project
Github user nickva commented on the issue:
https://github.com/apache/couchdb-couch-replicator/pull/47
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user iilyak commented on the issue:
https://github.com/apache/couchdb-couch-replicator/pull/47
All tests pass locally. +1
```
EUnit
module 'json_stream_parse'
module 'couch_replicator_worker'
module
