Closed robsonvn closed 6 years ago
I think we should create a branch from master which is the current old version and then master becomes the next version that we will merge our work in to for the next version.
Lets create a 1.0 branch from master as it is today and master will become 2.0
CouchDB ODM should stick with the 1.6 branch
@jwage I'm wondering the best approach for this PR. Since there are many changes between CouchDB version 1 and 2, should we split this library into different branches?