Re: Starting 2.0 Release Candidates

Yeah - awesome news. I will try to find a free time slot and try the tarball. Excited! Thanks so much to everyone making this happening! All the best Andy -- Andy Wenk RockIt! Hamburg / Germany GPG public key: https://pgp.mit.edu/pks/lookup?op=get=0x4F1D0C59BC90917D > On 13 Jul 2016, at

Re: 2.0 & Windows: status update

Ah - my mistake, sorry: I didn't merge it after all. The PR is outstanding at https://github.com/apache/couchdb-jiffy/pull/3, with some discussion between @kxepal and myself. There's a note to Paul there asking wiser heads than mine to make a decision on whether to add it upstream. Nick On Wed,

Re: Starting 2.0 Release Candidates

Hurray! :) Sent from my iPhone > On 13 Jul 2016, at 17:35, Jan Lehnardt wrote: > > Dear dev@, > > it’s been about three years in the making, but I think we are now at a point > where we can start the CouchDB 2.0 release candidate phase. > > Before we set the process in

Re: 2.0 & Windows: status update

Maybe I did something stupid with the PR. If I can get to a PC this evening I'll take a look. Nick On Wed, 13 Jul 2016 at 17:41, Paul Davis wrote: > That Jiffy error does seem like a conversion issue either from integer > widths or endianess. I don't remember seeing

Re: Starting 2.0 Release Candidates

> On 13 Jul 2016, at 18:35, Jan Lehnardt wrote: > > Dear dev@, > > it’s been about three years in the making, but I think we are now at a point > where we can start the CouchDB 2.0 release candidate phase. > > Before we set the process in stone, please give the tarball

Starting 2.0 Release Candidates

Dear dev@, it’s been about three years in the making, but I think we are now at a point where we can start the CouchDB 2.0 release candidate phase. Before we set the process in stone, please give the tarball linked below a try, as if were the CouchDB 2.0 release, and please report any issues

Re: 2.0 & Windows: status update

That Jiffy error does seem like a conversion issue either from integer widths or endianess. I don't remember seeing a patch for that on Windows and looking back I'm not seeing anything from after 2013 that looks related (in davisp/jiffy). Looking at the apache/jiffy repo we use merges so I'd think

Auto-Re: Starting 2.0 Release Candidates

Re: 2.0 & Windows: status update

I think I submitted a PR for that Jiffy problem a while back: it's some 32/64 bit issue. But I thought I'd also merged it. Unfortunately I'm away from any useful tools for the next few days so can't check myself, but take a look at the activity on the couchdb-jiffy repository. It's possible that

Re: 2.0 & Windows: status update

I took a look at the eunit failures and found that the entire couchdb_os_daemon_test module fails due to issues with how it expects to launch daemons. The main issue is that the primary test harness is a .escript file, which on *nix is magically parsed via the #!/usr/bin/escript header. On