Re: Testing a CouchDB 2.0 feature

> > > To: dev@couchdb.apache.org > > > > Subject: Re: Testing a CouchDB 2.0 feature > > > > > > > > Replying to my own email with more detail. > > > > > > > > The format of the 'queries' POST doc should look like: > > > > > > &

Re: Updating our New Committer template page - need permissions

7:18:48 AM > Subject: Re: Updating our New Committer template page - need permissions > > +1, change looks good. There are always areas in ComDev that can use > editorial improvements if you've got some more time... 8-) > > - Shane > > (Both emails came thru BTW) >

Updating our New Committer template page - need permissions

(Trying again from the correct email address) Hi all, Based on a discussion with other ASF members about improving our new committer templates and guidelines, I tried to commit a change to this page: https://community.apache.org/newcommitter.html Apparently I do not have permissions to

Updating our New Committer template page - need permissions

Hi all, Based on a discussion with other ASF members about improving our new committer templates and guidelines, I tried to commit a change to this page: https://community.apache.org/newcommitter.html Apparently I do not have permissions to publish the change to the public. You can view the

Re: Testing a CouchDB 2.0 feature

more detail. > > > > The format of the 'queries' POST doc should look like: > > > > { > > "queries" : [ > > { "startkey": "a", "endkey": "c"}, > > { "startkey": "q", "endke

Re: Testing a CouchDB 2.0 feature

Replying to my own email with more detail. The format of the 'queries' POST doc should look like: { "queries" : [ { "startkey": "a", "endkey": "c"}, { "startkey": "q", "endkey": "s"}

Re: Testing a CouchDB 2.0 feature

Looks like from the code your POST body should contain a 'queries' list or a 'keys' key-value pair. Here's an example of the latter that should now work under CouchDB 2.0 (see the answer, not the question):

Re: Cloudant document-level permissions feature?

ither Cloudant nor CouchDB 2.0 will support document-level > > permissions > > in the near future, sorry. > > > > B. > > > > > > > On 22 Aug 2016, at 00:37, William Edney > > > <bed...@technicalpursuit.com> > > wrote: > > > > > > Hi

[jira] [Commented] (COUCHDB-3101) Builtin reduce functions should not throw errors

[ https://issues.apache.org/jira/browse/COUCHDB-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419316#comment-15419316 ] Joan Touzet commented on COUCHDB-3101: -- One more +1 for {{null}} for the reasons stated above

Re: [PROPOSAL] CouchDB 2.0 log to ./var/log/couchdb.log by default

quire copy/truncate. > > It > > checks every 30s or so to see if the inode for its path changed and > > re-opens and starts writing to a new file if it has. > > > > On Tue, Aug 2, 2016 at 3:37 PM, Joan Touzet <woh...@apache.org> > > wrote: > > &

[jira] [Commented] (COUCHDB-3073) CouchDB 2.0 Blog Series: Release Candidates

[ https://issues.apache.org/jira/browse/COUCHDB-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411251#comment-15411251 ] Joan Touzet commented on COUCHDB-3073: -- Thanks Jenn! You are a true professional...thank _you_

[jira] [Commented] (COUCHDB-3073) CouchDB 2.0 Blog Series: Release Candidates

[ https://issues.apache.org/jira/browse/COUCHDB-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409050#comment-15409050 ] Joan Touzet commented on COUCHDB-3073: -- I should have mentioned that I don't know how to post

[jira] [Commented] (COUCHDB-3073) CouchDB 2.0 Blog Series: Release Candidates

[ https://issues.apache.org/jira/browse/COUCHDB-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408867#comment-15408867 ] Joan Touzet commented on COUCHDB-3073: -- Here's the blog post text. If you need it in another format

Re: CouchDB 2.0 Release Candidate 3

Windows build is ready! https://atypical.net/mm/couchdb-2.0.0-rc3.msi Also have one failing test in couch_log_writer_file_test, have reported it as COUCHDB-3092. -Joan - Original Message - From: "Jan Lehnardt" To: dev@couchdb.apache.org Sent: Thursday, August 4, 2016

[jira] [Created] (COUCHDB-3092) couch_log_writer_file_test failure on Windows

Joan Touzet created COUCHDB-3092: Summary: couch_log_writer_file_test failure on Windows Key: COUCHDB-3092 URL: https://issues.apache.org/jira/browse/COUCHDB-3092 Project: CouchDB Issue Type

Re: 2.0 & Windows: status update (all tests passing)

. Until then, if you want the latest installer, you can build it yourself :) All the best, Joan - Original Message - From: "Joan Touzet" <woh...@apache.org> To: dev@couchdb.apache.org Sent: Friday, July 15, 2016 6:58:39 PM Subject: Re: 2.0 & Windows: status updat

Re: [PROPOSAL] CouchDB 2.0 log to ./var/log/couchdb.log by default

o add that as a module > callback so it would work for stderr, file, and syslog. > >> On Aug 2, 2016, at 2:36 PM, Joan Touzet <woh...@apache.org> wrote: >> >> Presently, CouchDB 2.0 logs only to stderr. I have opened a PR >> to switch this behaviour to log to th

Re: [PROPOSAL] CouchDB 2.0 log to ./var/log/couchdb.log by default

seph.da...@gmail.com> wrote: >> >> Seems reasonable to me. I wonder if we should add a stdout log line that >> indicates where logs are going? Would be easy to add that as a module >> callback so it would work for stderr, file, and syslog. >> >>> On

[PROPOSAL] CouchDB 2.0 log to ./var/log/couchdb.log by default

Presently, CouchDB 2.0 logs only to stderr. I have opened a PR to switch this behaviour to log to the ./var/log/couchdb.log release-local file by default: https://github.com/apache/couchdb/pull/435 This behaviour is easily overridden in the default.ini/local.ini files if desired. I'm not sure

Re: CouchDB 2.0 blog series

ections, I'll be assigning these dates as the due > dates. > > > > Please let me know if these dates don’t work for you! > > > > Week 1 > Jul 25: The Road to CouchDB 2.0, Jan Lehnardt > Jul 27: Feature: Fauxton, Garren Smith > > Week 2 > Aug 1: The

Re: BigCouch merge status

Yes. Download our new 2.0.0-RC2 release candidate to get your hands on the merged code and let us know how your testing goes! We hope to have 2.0.0 released very, very soon now. -Joan - Original Message - > From: "Nestor Urquiza" > To: user@couchdb.apache.org >

[jira] [Created] (COUCHDB-3068) Docs fail to build with Sphinx 1.4+

Joan Touzet created COUCHDB-3068: Summary: Docs fail to build with Sphinx 1.4+ Key: COUCHDB-3068 URL: https://issues.apache.org/jira/browse/COUCHDB-3068 Project: CouchDB Issue Type: Bug

Re: CouchDB 2.0 blog series

Hi Jenn, I'll write about Release Candidates, as long as I can get a sentence or two in about the Windows port I just completed. :) I won't be available to write the post until August, though. Thanks, Joan - Original Message - > From: "Jenn Turner" > To:

[jira] [Commented] (COUCHDB-3040) Support CouchDB 2.0 release on Windows

[ https://issues.apache.org/jira/browse/COUCHDB-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384455#comment-15384455 ] Joan Touzet commented on COUCHDB-3040: -- I have completed work on the WiX-based installer and have

2.0 Windows Installer RC1

/README.md This repository will be moved into ASF infrastructure shortly. Enjoy, Joan Touzet

Re: New contributor need help

ase be sure you have the latest tarball to look at, or if you know how to use git, cloned from our apache/couchdb repository (master branch). We've recently fixed a couple of failing tests and you may be seeing issues we've already resolved. Best, Joan Touzet

[jira] [Commented] (COUCHDB-3040) Support CouchDB 2.0 release on Windows

[ https://issues.apache.org/jira/browse/COUCHDB-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382012#comment-15382012 ] Joan Touzet commented on COUCHDB-3040: -- As of the latest checkin to master, everything in {{make

Re: 2.0 & Windows: status update (all tests passing)

Trimming the long thread for readability... Good news, everyone! As of the latest checkin to master, CouchDB 2.0 builds correctly on Windows 64-bit! All eunit and javascript tests pass (or are skipped intentionally). This is a huge milestone! I especially want to thank Nick North and Dave

[jira] [Commented] (COUCHDB-3040) Support CouchDB 2.0 release on Windows

[ https://issues.apache.org/jira/browse/COUCHDB-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380268#comment-15380268 ] Joan Touzet commented on COUCHDB-3040: -- As of the latest commit to the couchdb repo (660c32f

Re: 2.0 & Windows: status update

at this one? (Paul?) -Joan - Original Message - From: "Joan Touzet" <woh...@apache.org> To: dev@couchdb.apache.org Sent: Tuesday, July 12, 2016 6:02:12 PM Subject: Re: 2.0 & Windows: status update Thanks, Paul. I'm starting to look at this today. In better news, current

Re: 2.0 & Windows: status update

gt; > > Sorry - I meant a single node cluster in that last message. And I meant >> > to >> > > sign my name correctly. >> > > >> > > Nick >> > > >> > > On Sun, 19 Jun 2016 at 16:56 Nick North <nort...@gmail.com

Re: Couchdb logging

Hi Michael, The 0.6257.467 part is the Erlang PID processing the result. Your best bet to time the duration of the request is to use haproxy ahead of CouchDB itself, and use haproxy's extensive logging features to get the timings you desire. Best regards, Joan Touzet - Original Message

Re: [DISCUSSION] Limiting the allowed size for documents

- Original Message - > Couch 1.x and Couch 2.x will choke as soon as the indexer tries to > process a too large document that was added. The indexing stops and > you have to manually remove the doc. In the best case you built an > automatic process around the process. The automatic process

Re: Need help on this "badmatch" error of couchdb 2.0

Hi Ying, It's the beam.smp process that is the main couchdb process. The other processes: epmd: Erlang port mapper daemon, acts as a name server for other Erlang hosts beam.smp: BEAM, the Erlang Virtual Machine, where couchdb runs cpu_sup: Erlang CPU supervisor process couchjs:

Re: Need help on this "badmatch" error of couchdb 2.0

Ying, Looks like your error is EMFILE, meaning too many open files as returned by the operating system. On OSX it appears you can up the limit: http://stackoverflow.com/questions/5377450/maximum-number-of-open-filehandles-per-process-on-osx-and-how-to-increase Try the command(s) listed there

Re: 2.0 & Windows: status update

*facepalm* :) Nothing private, just...didn't want to clutter the list. Sorry! - Original Message - > From: "Joan Touzet" <woh...@apache.org> > To: dev@couchdb.apache.org > Sent: Saturday, June 18, 2016 3:56:50 AM > Subject: Re: 2.0 & Windows: status update > > Replying off list. [SNIP]

Re: 2.0 & Windows: status update

ck North" <nort...@gmail.com> > To: dev@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> > Sent: Saturday, June 18, 2016 3:37:50 AM > Subject: Re: 2.0 & Windows: status update > > Hi Joan. This sounds like an improvement on my last Windows build &

Re: 2.0 & Windows: status update

Replying to my own email: dev/run is using the wrong path slashes for the path to the javascript/coffeescript view servers. I've submitted a PR and will merge if no one complains. Here is the latest set of test results if anyone still wants to volunteer to help me review them (both Eunit and JS,

Re: Extra reference in a commit message

No objection from me, if it makes things easier for you - as long as you are aware that you may get requests from customers saying "Hey, I see you used my bug tracker ticket id # in a CouchDB commit..." ;) -Joan - Original Message - From: "Ilya Khlopotov" To:

Re: 2.0 & Windows: status update

A small update on the testing front. I've tried replicating the animaldb from Cloudant to my local server, and things looked very ugly: https://gist.github.com/anonymous/f2a94234195f007c3049e27d942482c1 I've yet to dig into this failure; I'm posting it here in case anyone has the time to analyze

[jira] [Resolved] (COUCHDB-2950) Using CouchDB 1.6.1 on Windows. Trying to point...

[ https://issues.apache.org/jira/browse/COUCHDB-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet resolved COUCHDB-2950. -- Resolution: Won't Fix Assignee: Joan Touzet > Using CouchDB 1.6.1 on Windows.Try

2.0 & Windows: status update

Hello everyone, I'd like to update the community on the status of the 2.0 port to Microsoft Windows. There are three parts to this email: the build tools/chain themselves, support in CouchDB for the Windows build process, and testing results. I'll cover them in that order. -Joan Build

Re: _replicate vs. _replicator

Hi Ben, did anyone ever get back to you on this? I know that the core developers have a LOT of reservations about the _replicator database, primarily the fact that the backing store for a _replicator endpoint probably shouldn't be a database itself (though it could conceivably present a similar

Re: [ANNOUNCE] Nick Vatamaniuc elected as CouchDB committer

As I said on IRC...congratulations! Long overdue. -Joan - Original Message - > From: "Benjamin Bastian" > To: dev@couchdb.apache.org > Sent: Thursday, June 16, 2016 8:42:19 PM > Subject: Re: [ANNOUNCE] Nick Vatamaniuc elected as CouchDB committer > >

Re: 2.0 Code Freeze or branching 2.1?

Also +1, except for the work to get the Windows port running correctly. -Joan - Original Message - > From: "Michelle Phung" > To: dev@couchdb.apache.org > Sent: Thursday, May 26, 2016 7:23:46 AM > Subject: Re: 2.0 Code Freeze or branching 2.1? > > +1 > > -

Item for the CouchDB Newsletter

http://www.stilldrinking.org/proposal-for-new-rest-methods A bit of humour for the newsletter, maybe? :) -Joan

Re: [ANNOUNCE] Nolan Lawson elected as CouchDB committer

Congrats, Nolan! - Original Message - > From: "Robert Kowalski" > To: dev@couchdb.apache.org > Sent: Tuesday, April 19, 2016 12:04:22 PM > Subject: Re: [ANNOUNCE] Nolan Lawson elected as CouchDB committer > > Whohoo, congrats Nolan! :) > > On Tue, Apr 19, 2016 at 5:21

Re: make

Windows port. If the test suite is finally stable we'll do another pass of getting this to work - sans the Win 10 bash stuff since a) that's still in private release and b) Win 10 stinks. -Joan - Original Message - > From: "Jan Lehnardt" > To: dev@couchdb.apache.org > Sent:

Re: Adam Kocoloski is now an IBM Fellow

Congrats! - Original Message - > From: "Jan Lehnardt" > To: "dev@couchdb.apache.org Developers" > Sent: Friday, April 15, 2016 4:50:10 AM > Subject: Adam Kocoloski is now an IBM Fellow > > Hey all, > > our own Adam made IBM Fellow! He’s now one

Re: On dependency management and CI issues associated with it

Based on this information, are we in violation of ASF requirements? Can anyone clarify for me what we actually need to be doing here? -Joan - Original Message - > From: "Garren Smith" <gar...@apache.org> > To: dev@couchdb.apache.org, "Joan Touzet" <

Re: On dependency management and CI issues associated with it

Garren, correct me if I'm wrong but Fauxton depends on a large number of JS dependencies that we don't keep copies of, correct? Or is it just for the build process? -Joan - Original Message - > From: "Alexander Shorin" > To: dev@couchdb.apache.org > Sent: Wednesday,

Re: make

Agreed, good enough for now. - Original Message - > From: "Jan Lehnardt" > To: "dev@couchdb.apache.org Developers" > Sent: Wednesday, March 30, 2016 3:57:01 PM > Subject: make > > Hey all, > > last year I endeavoured to make the 2.0 build

Re: Calculating Revision IDs outside erlang (proposal to add {minor_version, 1} to the calc)

Hey Mike, As mentioned on IRC I'd like to see some test cases in our suite to help ensure we don't regress on this in the future. Specifically, I think it'd be good to ensure consistent revs on a handful of indicative docs. There's nothing saying we can't change how we do this in the future,

Re: Public endpoint when couch_httpd_auth.require_valid_user=true

In CouchDB 2.0 there should be /_up . I'd consider it a bug if that endpoint required a valid user. /_up returns {"status":"ok"} if everything is copacetic. -Joan - Original Message - > From: "Alexander Shorin" > To: user@couchdb.apache.org > Sent: Thursday, March 10,

Re: Happy Birthday Garren!!

Jumping on the bandwagon a bit late butHappy Happy! -Joan - Original Message - > From: "Garren Smith" > To: dev@couchdb.apache.org > Cc: andyw...@apache.org, "Garren Smith" > Sent: Friday, February 12, 2016 12:27:05 PM > Subject: Re: Happy

Re: Applied for official Docker image

I've not been following this message trail carefully, but I have a question. Does the docker image run 3 instances within the same image, or is it a single node version? The reason I ask is that, in deployment, which is where I would expect docker to shine, you'd **NEVER** want to run 3 nodes on

Re: Signal Handing

Feel free to kill -9 couchdb if you want. There is no special "graceful" shutdown for couchdb and it doesn't matter given our crash-only architecture. If SIGSTOP makes you feel better, feel free to cargo cult that as a solution. Makes no difference ;) -Joan - Original Message - > From:

Re: Compiling snappy under Windows

I agree we should avoid re-introducing autoconf to the build process. Hopefully we can fix this with a simple set of #ifdefs in a header file somewhere that defines ssize_t (or anything else we need) appropriately, or dig into the MS SDK for any references available and include compat header

Re: how to force flush a db?

One thing to note is that your views and your DB may be in different states when you pull files off the HDD sequentially, if they're large. If your views are "newer" than the DB file you have, it could cause issue. I recommend copying the .views subdirectory FIRST, then copying the database file.

Re: [POC] Mango Catch All Selector

rustrating experience, and I don't think that a reputation for > >>>> "works until you cross a threshold, and then it doesn't, but only in > >>>> production" is a good thing to move towards. > >>>> > >>>> Perhaps something like add

Re: [POC] Mango Catch All Selector

Hi Robert, I've been thinking about this one for the week or so, and I have a simple suggestion: Add the query parameter slow=true to enable this behaviour. This meets all the original requirements: 1. It is not default behaviour 2. You can grep the log files for the word 'slow' and find

Re: couchdb and static site generation?

You might want to check out Diana Thayer's Quilter: https://github.com/garbados/quilter Written in node.js as requested. -Joan - Original Message - > From: "bryan rasmussen" > To: user@couchdb.apache.org > Sent: Friday, January 1, 2016 2:23:52 PM > Subject:

Re: [PROPOSAL] Deprecate global functions in query server

> -2. still doesn’t solve that `function() {}` is not valid JavaScript > and doesn’t work in newer SpiderMonkeys or other engines. But that > might be out of scope. IMO if you're going to tweak anything in the query definitions, you HAVE to fix this - it's a bridge to us using any other engine

Re: Weekly News timing

It's fine :) See you tomorrow. -Joan - Original Message - > From: "Katha" > To: marketing@couchdb.apache.org > Sent: Thursday, November 26, 2015 6:18:49 AM > Subject: Weekly News timing > > Hi all, > > quick question - hope it will be ok, if I send out the

Re: Retiring AdvocateHub

Thanks Noah for getting it started, and Harald for driving this further! CouchDB does need a social media presence, and AdvocateHub is a great gamification strategy to drive that further. -Joan - Original Message - > From: "Harald Kisch" > To:

Re: MapReduce in CouchDB

ick LGPL either). Please reconsider your licensing terms. Thanks, Joan Touzet

Re: [PROPOSAL] Allow rewrites to be JS function

- Original Message - > From: "Harald Kisch" > To: dev@couchdb.apache.org > Sent: Tuesday, October 20, 2015 11:45:18 AM > Subject: Re: [PROPOSAL] Allow rewrites to be JS function > > Extendability and Upgradability with npm - what could be more > extendable > and

Re: Fauxton Windows developer question

Hi Robert, I'm presently migrating our one Makefile left in couchdb to a Windows NMakefile, which uses a different syntax. git shell works but has enough problems that I don't want to rely on it. Sometimes it's almost as much work to debug a GNU Makefile running under cygwin as it is to rewrite

[jira] [Closed] (COUCHDB-2343) /_config/admins/username fails on master

[ https://issues.apache.org/jira/browse/COUCHDB-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joan Touzet closed COUCHDB-2343. > /_config/admins/username fails on mas

Re: [ANNOUNCE] Garren Smith joins the PMC

Congratulations, Garren! Glad to have you with us. -Joan - Original Message - > From: "Andy Wenk" > To: dev@couchdb.apache.org > Sent: Monday, October 19, 2015 9:41:35 AM > Subject: Re: [ANNOUNCE] Garren Smith joins the PMC > > Hey Garren, > > finally! welcome on

Re: [ANNOUNCE] Michelle Phung joins the PMC

What a climb, Michelle! Super stoked to have you in the PMC. -Joan - Original Message - > From: "Andy Wenk" > To: dev@couchdb.apache.org > Sent: Monday, October 19, 2015 9:42:15 AM > Subject: Re: [ANNOUNCE] Michelle Phung joins the PMC > > Hey Michell - cool to

Re: PMC members list

Everyone can read the bylaws for the Apache CouchDB project here: https://couchdb.apache.org/bylaws.html -Joan - Original Message - > From: "Jan Lehnardt" > To: dev@couchdb.apache.org > Sent: Tuesday, September 22, 2015 6:16:18 AM > Subject: Re: PMC members list > >

Re: The future of couchapps

I'll concur with Alex here. My survey of the PMC members so far has resulted in 100% of us in agreement with Jan's comments. This is not a power play, it is a logical, reasoned decision with many factors that play a part -- not the least of which is that there are so many great web frameworks out

Re: [PROPOSAL] Remove oAuth for 2.0

I was one of the last people to leverage the CouchDB OAuth provider in a commercial setting. That project ended nearly 4 years ago now. What we have today is "2-legged" OAuth 1.0 compatibility that grew out of functionality Ubuntu was looking for with the now-dead UbuntuOne desktop functionality.

Re: “Yes, and…”, not “But…” (Was: [PROPOSAL] Create des...@couchdb.apache.org mailing list)

Hey there. One thing we need to consider, Michelle: The Bylaws for CouchDB and the Apache community guidelines state that all official *decisions* for the project must be reached on an official mailing list - not a Slack instance or IRC or an in- person meeting. We've (the PMC have) fought with

Re: “Yes, and…”, not “But…” (Was: [PROPOSAL] Create des...@couchdb.apache.org mailing list)

Hit send too soon, see below - Original Message - > From: "Joan Touzet" <woh...@apache.org> > To: dev@couchdb.apache.org > Sent: Tuesday, September 15, 2015 10:39:01 PM > Subject: Re: “Yes, and…”, not “But…” (Was: [PROPOSAL] Create > des...@couchdb.ap

Re: [VOTE] WHY/HOW/WHAT

My vote and reasoning matches Michelle's. Would be happy to see more options and an additional vote, if people prefer. -Joan - Original Message - > From: "Michelle Phung" > To: marketing@couchdb.apache.org > Sent: Tuesday, September 15, 2015 4:07:54 PM > Subject:

Re: CouchDB _rewrite

Proedurally, CouchDB 2.0 is effectively in feature freeze - we need to get it out the door, it is far overdue. Looking at changing basic functionality like _rewrite can come after 2.0 is done, in the 3.0 timeframe. -Joan - Original Message - > From: "Johs. E" > To:

Re: CouchDB _rewrite

Proedurally, CouchDB 2.0 is effectively in feature freeze - we need to get it out the door, it is far overdue. Looking at changing basic functionality like _rewrite can come after 2.0 is done, in the 3.0 timeframe. -Joan - Original Message - > From: "Johs. E" > To:

Re: CouchDB Weekly News – Submissions

Hi Katharina, My talk's video recording is now online. https://www.youtube.com/watch?v=iKKkKkWATDo -Joan - Original Message - > From: "Katharina Jockenhöfer" > To: u...@couchdb.apache.org, market...@couchdb.apache.org, > dev@couchdb.apache.org > Sent:

Re: [ANNOUNCE] Clemens Stolle elected as CouchDB committer

Welcome! - Original Message - From: Klaus Trainer klaus_trai...@posteo.de To: dev@couchdb.apache.org Sent: Friday, August 28, 2015 6:06:54 AM Subject: Re: [ANNOUNCE] Clemens Stolle elected as CouchDB committer Welcome Clemens :) On 08/27/2015 01:47 PM, Robert Kowalski wrote:

Re: Brainstorm: A new CouchDB tag-line?

Just a point that The database that syncs is PouchDB's tagline. Probably should take it out of the running. I knew I'd seen it somewhere :D The PMC will take the feedback from this discussion and decide what to do next. A vote is not necessarily the best next step here. -Joan - Original

Brainstorm: A new CouchDB tag-line?

Hey everyone, I don't know where we landed on this discussion last time, but I'm fairly sure we didn't come to any sort of agreement. Our current tag-line for CouchDB is pretty unwieldy: Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and

Re: couchdb question

will ever be deleted) but you can always undelete any document you need. The choice is yours depending upon the data access methodology you want. Hope this helps, Joan Touzet

Re: Windows PR #2

And letting people know I'll validate this Wednesday, I am unavailable Tuesday. Thanks Paul! -Joan - Original Message - From: Paul Davis paul.joseph.da...@gmail.com To: dev@couchdb.apache.org, Joan Touzet woh...@apache.org Sent: Tuesday, July 14, 2015 2:43:13 AM Subject: Re

Re: Windows PR #2

: Dave Cottlehuber d...@skunkwerks.at To: dev@couchdb.apache.org Sent: Sunday, July 12, 2015 3:29:59 AM Subject: Re: Windows PR #2 On Sun, 12 Jul 2015, at 02:06 AM, Joan Touzet wrote: https://github.com/apache/couchdb-couch/pull/69 Same thing. Message to follow with important release

Re: Windows PR #2

- Original Message - From: Dave Cottlehuber d...@apache.org To: dev@couchdb.apache.org Sent: Monday, July 13, 2015 4:19:58 PM Subject: Re: Windows PR #2 On Mon, 13 Jul 2015, at 09:56 PM, Joan Touzet wrote: I intend to publish it in detail once we have the khash issue sorted out

Re: Windows build blocked by khash NIF

@couchdb.apache.org, Joan Touzet woh...@apache.org Sent: Saturday, July 11, 2015 10:08:43 PM Subject: Re: Windows build blocked by khash NIF There’s a comment in the code where we declare make_hash2() which states // There's a pending patch to expose this in the NIF API in newer Erlangs. Did

Re: Windows build blocked by khash NIF

Alex says: On Sun, Jul 12, 2015 at 3:14 AM, Joan Touzet woh...@apache.org wrote: 1) Build a custom beam.smp.dll on Windows that exports make_hash2 Sounds as the right solution, but how it will complicate build process? It means that Windows builds have to have a custom built Erlang

Windows build blocked by khash NIF

Hello everyone, Progress on the Windows build was surprisingly smooth, thanks to native MSVC build chain support in rebar, and improved in the version I am running locally (2.6.0). Unfortunately, we have a release blocker on Windows in the khash NIF. This NIF expects to call an Erlang BEAM VM

Windows PR #1

https://github.com/apache/couchdb-b64url/pull/3 Can I get a +1 before I merge this? More Windows build details to come.

Windows PR #2

https://github.com/apache/couchdb-couch/pull/69 Same thing. Message to follow with important release-blocking info.

Re: [PROPOSAL] Workflow with forked repos

Alex wrote: - When need knocks the door, we merge upstream into master, where our local changes happens; We will need to be careful about this not to undo the changes we need for ourselves, for instance re-introducing a binary rebar or clobbering our .travis files as you point out. As such

[master] rebar failing get-deps on win64

Hi there, I'm in the process of trying to get CouchDB 2.0 ported to Windows. I've reproduced the configure script in PowerShell script and am proceeding to work on the Makefiles, but I'm running into a get-deps issue where it fails to pull the couch_index deps. As my time is limited on this

Re: [master] rebar failing get-deps on win64

of such a make target? There's no other way to readily recover from a failed get-deps (due to e.g. poor network connectivity during a git clone) -Joan - Original Message - From: Joan Touzet woh...@apache.org To: dev@couchdb.apache.org Sent: Tuesday, June 30, 2015 11:05:23 PM Subject: [master

Re: ApacheCon Core Big Data EU

I have two talks submitted, one is a tutorial for CouchDB 2.0 (Big Data) and one is on Communities and Codes of Conduct (Core). My arm could be twisted to propose a third, but without a funding source to attend (TAC is still down and I haven't heard back from the Linux foundation) I will be

[jira] [Commented] (COUCHDB-2390) Fauxton config, admin sections considered dangerous in 2.0

[ https://issues.apache.org/jira/browse/COUCHDB-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14606230#comment-14606230 ] Joan Touzet commented on COUCHDB-2390: -- /cc @davisp [~rnewson] [~janl] If we

Re: CouchDB utc_id behavior

now() is not guaranteed to be monotonically increasing if the system clock rolls backwards, which various things can cause. You should look into setting up ntpd for your two machines at the very least. -Joan - Original Message - From: Nick North nort...@gmail.com To:

Re: [PROPOSAL] GitHub issues

Personally I'm -0.5 on this. The system of record needs to remain JIRA. GH Issues is no replacement for JIRA; the fidelity of the system is vastly different. We need more people cleaning up JIRA and making that environment make more sense, not to add clutter to the pile by enabling issues.

Re: [PROPOSAL] GitHub issues

The system of record needs to remain JIRA. Why? Because (ASF Member hat on) if GH goes away, the project would be crippled, severely so. Losing the institutional memory of what is going on is a serious problem. Because otherwise you need to migrate a couple thousand bugs out of JIRA,

<    7   8   9   10   11   12   13   14   15   16   >