I have a bug we are recently running into.
Our CI system for Fauxton uses fresh builds of 2.0. We _sometimes_ get
a 503 error from Couch when we try to create our test database. We
boot Couch and wait 30 seconds, raising to 120 seconds did not help.
Example build: https://travis-ci.org/robertkowa
> blockers, not new work. And, yes, I still believe you are proposing
> something major, with ramifications that require real thought.
>
Thanks guys :)
Mike
What Bob said, this thread isn’t about designing new features, this is
to get 2.0 — finally — out.
Best
Jan
--
> On 19 Apr 2016, at 04:24, Michael Fair wrote:
>
> I understand it might seem huge, but I'd like to confirm that is actually
> huge...
>
> I'm proposing that (1) We confirm/deny that
Please move this to its own thread, we're discussing the final, existing 2.0
blockers, not new work. And, yes, I still believe you are proposing something
major, with ramifications that require real thought.
After 2.0, I'm sure we'll want to discuss improving interoperability,
especially around
I understand it might seem huge, but I'd like to confirm that is actually
huge...
I'm proposing that (1) We confirm/deny that a sufficiently advanced CouchDB
plugin; using the existing plugin system could duplicate the effects of a
replication call. That only requires someone who knows to say yes
Respectfully, no.
What you propose is huge and will take considerable time to design. 2.0 is two
years late already.
We're all for encouraging interoperability but we'll have to address it in a
later release.
> On 18 Apr 2016, at 21:23, Michael Fair wrote:
>
> Before RC1 gets locked in; wo
Before RC1 gets locked in; would anyone be opposed to adding replicating
with non-erlang based datastores; (I'm thinking java (android/desktops),
c#, python, c, objective-c (ios) - not that language matters at all) be a
named feature for the 2.0 series?
Specifically this wouldn't mean writing any
On Mon, Apr 18, 2016 at 1:35 PM, Andy Wenk wrote:
>> On 18 Apr 2016, at 10:57, Jan Lehnardt wrote:
>>
>> Hey all,
>>
>> we are getting close to 2.0. In the list of blockers, there are only two
>> issues left that aren’t docs, that we’ll need some concerted help with:
>>
>> https://issues.apache.
> On 18 Apr 2016, at 10:57, Jan Lehnardt wrote:
>
> Hey all,
>
> we are getting close to 2.0. In the list of blockers, there are only two
> issues left that aren’t docs, that we’ll need some concerted help with:
>
> https://issues.apache.org/jira/browse/COUCHDB-2863
it seems that there is al
Hey all,
we are getting close to 2.0. In the list of blockers, there are only two issues
left that aren’t docs, that we’ll need some concerted help with:
https://issues.apache.org/jira/browse/COUCHDB-2863
https://issues.apache.org/jira/browse/COUCHDB-2834
If anyone as any spare cycles looking a
10 matches
Mail list logo
