Re: [Lazy Consensus] Move from JIRA to GitHub Issues

+1 On Thu, May 18, 2017 at 2:23 PM, Joan Touzet wrote: > Hi Anthony, > > Unfortunately, having a JIRA account is not the same as having an > Apache account. > > You have to be elected an official CouchDB Committer to obtain an > Apache account. New committers are elected by

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

Hi Anthony, Unfortunately, having a JIRA account is not the same as having an Apache account. You have to be elected an official CouchDB Committer to obtain an Apache account. New committers are elected by the PMC according to the rules set out in the CouchDB bylaws:

Re: Truncated response when POST a _changes query

Hi Nasser, I'm afraid not yet. Please remember that CouchDB is a volunteer-run project, and we wear many hats. There are options for commercial support of CouchDB if you need urgent support. Best regards, Joan - Original Message - From: "Nasser Ebrahim" To:

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

Awesome. +1 From: Joan Touzet To: CouchDB Developers , CouchDB Users Date: 2017/05/17 12:38 PM Subject:[Lazy Consensus] Move from JIRA to GitHub Issues Hi everyone. As most of you know, a few

[NEWS] The CouchDB weekly news for May 18 is out!

Hello and happy Thursday! The Apache CouchDB weekly news is now live at: https://blog.couchdb.org/2017/05/18/couchdb-weekly-news-may-18-2017/ Highlights include new releases in the CouchDB ecosystem, some new discussions,

Re: A tale of two Dockers: couchdb-ci and couchdb-docker

We use a CouchDB docker container for testing PouchDB and Fauxton. So my usage and requirements for docker instances are pretty narrow. I just need a development image that is up to date with master. Joan created this one https://hub.docker.com/r/couchdbdev/debian-8-dev/ based off the

Re: Descending replication

What is the next step for something like this? I'm guessing a github ticket would be great. What kind of internal changes would be required? On Thu, May 4, 2017 at 10:22 PM, Robert Samuel Newson wrote: > Hi, > > I agree this would be a great option, even a better default. >

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

Yes!!! On Wed, May 17, 2017 at 9:38 PM, Joan Touzet wrote: > Hi everyone. > > As most of you know, a few months ago we moved many of our primary > repositories from primary Apache hosting to primary GitHub hosting. A > major reason we did so was to leverage the better user

Re: Truncated response when POST a _changes query

Hi Joan and Robert, Did you get a chance to look into the logs? Please let us know if you need any further information or diagnostic data to progress this issue. Thank you, Nasser Ebrahim On 5/9/17 2:42 PM, Nasser Ebrahim wrote: Thank you Joan and Robert for your inputs. We have tested

Angående: [Lazy Consensus] Move from JIRA to GitHub Issues

+1 Sendt fra Yahoo Mail på Android Den ons. 17. mai. 2017 kl. 21.38 skrev Joan Touzet: Hi everyone. As most of you know, a few months ago we moved many of our primary repositories from primary Apache hosting to primary GitHub hosting. A major reason we did so was to

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

+1 Nick > On 18 May 2017, at 07:01, Elisiano Petrini wrote: > > +1  > > Best Regards, > Elisiano Petrini > >> On May 17, 2017, at 9:38 PM, Joan Touzet wrote: >> >> Hi everyone. >> >> As most of you know, a few months ago we moved many of our