to consider. The alternative, full removal
> of the feature, has its advocates too.
>
> --
> Robert Samuel Newson
> rnew...@apache.org
>
> On Fri, 1 Feb 2019, at 17:21, Eli Stevens (Gmail) wrote:
> > A couple other topics that I think would make sense to discuss:
> >
&g
A couple other topics that I think would make sense to discuss:
- How to manage edge-case performance or capability regressions resulting
from the switch. My former team couldn't use 2.x in production until
2.2 due to a handful of these kinds of issues. What's going to happen when
users blocked du
I'd like to request that there be threads where it's appropriate to discuss:
- Managing the refactoring/merge process to avoid the previous situation
where 1.x was mostly dead, but 2.x wasn't going to land for a few years.
- Other features to deprecate at the same time as losing JS reduce (I
assum
(I should note that since I'm the point person for CouchDB at my
company, I end up using I/we a bit interchangeably.)
On Sun, May 21, 2017 at 3:07 AM, Jan Lehnardt wrote:
>> On 21. May 2017, at 04:17, Eli Stevens (Gmail) wrote:
>>
>> I realize that this might be somewhat
Please take this as a single data point from an end user:
This approach will probably result in my company declining to upgrade
to CouchDB 2.1, and instead waiting for 2.2 in hopes that the test
suite will be in a more stable state by then. This is somewhat ironic,
given that my company is also sp
As a user and occasional bug reporter, I welcome the change.
Searching for existing issues in JIRA was painful, mostly due to
feeling like I had to repeat myself in saying that I wasn't interested
in any of the other projects on the instance.
On Wed, May 17, 2017 at 1:59 PM, Jan Lehnardt wrote:
Hello devs,
My company is interested in contracting out work to produce .deb
packages for CouchDB 2.0. We have a hard requirement for Ubuntu 16.04,
and would additionally like 12.04 if possible (my understanding is
that this is more difficult, due to the age of the release).
The intent is that th
ng for 2.0 would be on-topic for the list),
so I figure it's best to ask.
Thanks,
Eli
On Sat, Jan 21, 2017 at 2:30 AM, Robert Samuel Newson
wrote:
> Gentle reminder that this is the developer mailing list for CouchDB.
>
> B.
>
>> On 21 Jan 2017, at 05:04, Eli Stevens (Gmail)
all of
> the different use cases that are out there, so if our current offering
> doesn't cover yours we'd still like to know more about it so we can try and
> improve it.
>
> On Tue, Jan 17, 2017 at 12:37 PM, Eli Stevens (Gmail)
> wrote:
>
>> Thanks for fo
alled, and then left alone."
Do you know if snaps have server/enterprise usage as a use-case, or
are they aimed squarely at user/desktop applications?
Cheers,
Eli
On Tue, Jan 17, 2017 at 7:20 AM, Michael Hall wrote:
> On 12/20/2016 01:56 PM, Eli Stevens (Gmail) wrote:
>> On Tue, Dec
On Wed, Dec 21, 2016 at 3:04 AM, Jan Lehnardt wrote:
>> On 20 Dec 2016, at 19:56, Eli Stevens (Gmail) wrote:
>> The impending EOL and unavailability of CouchDB 2.0 might cause us to
>> revisit that decision.
>
> The what?
Sorry, that was unclear, due to having relie
On Tue, Dec 20, 2016 at 9:16 AM, Michael Hall wrote:
> On 12/19/2016 06:23 PM, Eli Stevens (Gmail) wrote:
>> I'll have some people on my team get on that as soon as we have time;
>> probably after the new year.
>>
>
> Thanks! If they have any questions or need help
On Fri, Dec 16, 2016 at 11:47 AM, Michael Hall wrote:
> You can try the snap I built, it's on
> http://people.ubuntu.com/~mhall119/snaps/
>
> Download it and run "snap install --dangerous couchdb_2.0_amd64.snap"
> (assuming you're on Ubuntu 16.04 or later)
I'll have some people on my team get on
Very cool. We've been wanting a packaged version of 2.0 for a while.
This might be jumping the gun, but I'm curious to know what the story
is for upgrading from previous, non-snap versions is, and how
post-snap upgrades will be handled. At first glance, it seems like
there is a trade off between h
When bitten by similar issues, I've found that moving large data
fields to attachments can work around the size issue. As long as you
don't need that data for indexing, it works well.
Cheers,
Eli
On Fri, Nov 25, 2016 at 2:10 AM, Reddy B. wrote:
>
>
>
> I can see that erl.exe actually crashes du
FWVLIW, I'd rather keep the tests active, and have the release happen
with not all tests passing. A failing test doesn't have to be a
release blocker (I mean, this PR is clearly stating as much). Maybe
add a known issue in the release notes or something.
If the policy is "the tests must pass" with
Nodes in the cluster do not replicate to one another.
Replication takes place between databases. A single node isn't a
database; a clustered database spans multiple nodes.
Each node has a black-box lump of data that happens to have a fraction
of a database inside, but that's an implementation det
On Tue, Apr 19, 2016 at 12:09 AM, Jan Lehnardt wrote:
> Discussions about this are about two years old and now
> is not the time to revisit them.
I probably didn't do a good job of conveying my stance earlier, but I
wholeheartedly agree with this position.
Thanks,
Eli
Honestly, the entire topic feels over-thought to me. If someone sets
up a database, has it listen to a port that's open to the internet,
and doesn't set a password... The situation is pretty much hopeless.
There's zero chance that *this* is the only security hole that they
have, and IMO it's kinda
Can't wait to finally see some movement on that Mongo-on-MyISAM work
I've heard so much about!
On Thu, Mar 31, 2016 at 11:51 PM, Александр Опак
wrote:
> 😀
>
> 2016-04-01 9:51 GMT+03:00 Ameen :
>
>> This is what gave it away!
>>
>> > I’m glad I’m finally done with Erlang and I can’t wait to
>> get
Personally, I think that the project would benefit from having the OS
packagers get pulled in towards the project more (ideally, producing
.rpm and .deb etc. as part of the release process).
To that end (and as previously mentioned), we've contracted with Dave
Cottlehuber to produce Ubuntu 15.10/1
On Mon, Jan 25, 2016 at 11:10 AM, Alexander Shorin wrote:
> On Mon, Jan 25, 2016 at 9:59 PM, Eli Stevens (Gmail)
> wrote:
>> The intent was to hopefully have the build scripts, etc. folded back
>> into the main repo to make it easier for future releases to have
>> offici
On Mon, Jan 25, 2016 at 8:06 AM, Clemens Stolle
wrote:
>> Am 25.01.2016 um 11:44 schrieb Alexander Shorin :
>> We don't provide any PPA builds to use, especially for 2.0, today.
>> Ubuntu vs debian - doesn't matter for me.
>
> I was referring to this PPA
> https://launchpad.net/~couchdb/+archive/
Not sure if I should keep marketing@ on the CC list; erred on the side
of inclusion.
Docker didn't exist when we started our project, and we've not felt
the need to start using it, so it's a hurdle (a small one, but enough
that we've not bothered to alter our build scripts to include the new
depen
Just wanted to chime in here as a user - I've run into similar
behavior from CouchDB with the reduce-not-reducing-enough heuristic,
where stuff I was working on went smoothly in dev, but stopped once
real load was pushed through it (thankfully for me, that was in
testing, rather than released to cu
week for you guys.
>
> Try the github repo in the meantime though!
>
> :)
> Michelle
>
>> On Sep 16, 2015, at 8:32 PM, Eli Stevens (Gmail)
>> wrote:
>>
>> I just (mostly) followed the instructions at (except for the -g part,
>> since I didn't wa
le endless.
>
> I thought we fixed the problem you described though.
> Did you pull from https://github.com/apache/couchdb-fauxton, the master
> branch?
>
> Michelle
>
>
>
>> On Sep 16, 2015, at 5:50 PM, Eli Stevens (Gmail)
>> wrote:
>>
>> Whe
ug 19, 2015 at 11:34 AM, Eli Stevens (Gmail)
wrote:
> I agree with kexpal's comment on the PR; large documents would make
> this very, very painful.
>
> I was asking for a view checkbox that would result in a 3rd column for
> view results (key / value / optional doc) that defaulted
It would be helpful for me (and perhaps others, I think) if more
examples/details were given about the intended audience and use.
The emphasis on screenshots makes me suspect that "design" means
"UI/CHI/visual design" rather than "software architecture," but it's
still not clear exactly what would
9:55 AM, James Dingwall
> wrote:
>> Eli Stevens (Gmail) wrote:
>>>
>>> On Tue, Aug 18, 2015 at 1:11 AM, James Dingwall
>>> wrote:
>>>>
>>>> I get the impression that more whizzy effects (fade in/out, sliding divs
>>>> etc) have bee
On Tue, Aug 18, 2015 at 1:11 AM, James Dingwall
wrote:
> I get the impression that more whizzy effects (fade in/out, sliding divs
> etc) have been added which don't play nicely with remote sessions with
> low bandwidth so a preference to use more basic transitions would be useful.
+1
Note that i
Hi Michelle,
Overall, sounds great. I'll reply inline where needed:
On Mon, Aug 17, 2015 at 10:58 AM, Michelle Phung wrote:
> Feedback #2: Default _all_docs page doesn’t show enough relevant information
> Fair enough, this is something I think we should default with
> include_docs=true,
Hi,
Thanks for asking for user feedback!
I just installed the default new(ish?) fauxton via npm, etc. from the
instructions at https://www.npmjs.com/package/fauxton (not sure if
that's as up to date as it could be). Here are my (hopefully
constructive) opinions. In general, I agree with a lot of
Just a note: anyone actually *upgrading* from 1.6 isn't going to have
anything but a cluster-of-one, so I think that limiting the web UI to
cluster-of-one setups is perfectly fine (nobody is losing capability).
Any cluster-of-N deployment is going to be new by definition, so
having to use a new set
Thank you for your continued work on this!
Eli
On Thu, Jun 25, 2015 at 1:17 AM, Dave Cottlehuber wrote:
> Hi folks,
>
> The Ubuntu dev PPA [1] has a minor update to fix an issue reported
> privately by Shawn Parrish, that prevents the daemon running correctly
> on a minimal Ubuntu 14.04 install.
A quick wiki-and-google search didn't turn up the breaking changes
document; is that publicly available yet? If so, where?
Thanks,
Eli
On Wed, Jun 17, 2015 at 8:50 AM, Jan Lehnardt wrote:
> Hey all,
>
> Alexander, Bob and I had a bit of a brainstorming session today on what is
> missing to get
Paul Davis: +0.5
Nick Pavlica Logo 1: +1
Nick Pavlica Logo 2: -1
Nick Pavlica Logo 3: -1
Brad Noble: +0
Sean Barclay Logo 1: -1
Sean Barclay Logo 2: -1
Sean Barclay Logo 3: -1
Apache CouchDB (old logo): +1
Constantin Angheloiu: +0.5
On Wed, Apr 8, 2015 at 8:20 AM, Benoit Chesneau wrote:
> -1 Paul
Hey all,
I haven't seen any discussion of this topic for a while now. I had
asked about it on IRC a while back, and didn't get an indication of
any firm plans.
What's the story for upgrading 1.6 DBs to 2.0?
We have a bunch of customer systems that are behind their corp
firewalls that we're going
The Apache CouchDB application verifies for me (sig matches too). Thanks!
I'm on mavericks, and sadly don't have any earlier versions to test on.
Eli
On Sat, Sep 13, 2014 at 2:35 PM, wrote:
> On Wed, 10 Sep 2014, at 11:43 PM, Andy Wenk wrote:
>> Jan - everything is fine - don't worry! I will
FYI, I'm happy to try packages on my system, provide more detailed info, etc.
I've got a tradeshow and a vacation packed into the next two weeks, so
my response time might be a bit slow, but I should be checking email,
etc. Feel free to email me directly if desired.
On Wed, Sep 10, 2014 at 2:28 P
Software OS X 10.9.4 (13E28)
Running on a late 2010 Macbook Pro. 2.66 GHz Intel Core i7-2600, so it's 64 bit.
On Mon, Sep 1, 2014 at 2:48 PM, Jan Lehnardt wrote:
>
> On 01 Sep 2014, at 23:42 , Eli Stevens (Gmail) wrote:
>
>> OSX. Sigs check, but after copying the app
OSX. Sigs check, but after copying the app to /Applications and trying
to run it, I get the following dialog:
Problem Running CouchDB
CouchDB Server doesn't seem to be operating properly. Check Console
logs for more details
[Quit] [Retry]
Trying to run it from the console:
14:35:32 elis@oort cou
A non-binding +1. :)
I had a couple of questions that didn't have obvious answers in the text.
First, what is the intended interaction between "explicitly
honour[ing] diversity in: ... political beliefs, ... religion" when
the beliefs in question explicitly contradict the diversity statement?
I
One quick thought:
Clustered couchdb has been a while coming, and still has a while to go
before it's ready; I would suggest not saddling the release with
additional changes or requirements, especially if they're the type
that can be bikeshedded to death (stuff like API changes can take a
while to
https://dist.apache.org/repos/dist/dev/couchdb/binary/mac/1.6.0/rc.5/
OSX 10.9.3, all steps pass. +1
Cheers,
Eli
On Tue, Jun 3, 2014 at 6:21 AM, Jan Lehnardt wrote:
>
> On 27 May 2014, at 09:46 , Dirkjan Ochtman wrote:
>
>> Dear community,
>>
>> This is a request to prepare binaries for the 1
It would be nice if
https://github.com/apache/couchdb/commit/d81619033206f09a774072dc2f84f7f275b12496
were included in 1.6; after casual inspection, it doesn't seem like
that commit is on the branch.
Cheers,
Eli
On Thu, Apr 10, 2014 at 3:15 AM, Dirkjan Ochtman wrote:
> On Thu, Apr 10, 2014 at 11
Installs fine, old DBs still visible, install verifies.
It didn't automatically open in my browser, though (FF, beta channel).
I might have disabled that in a previous release? Not sure if that
was even possible. The checkbox in the menu was unchecked.
+1
Eli
On Thu, Apr 3, 2014 at 11:30 AM,
I can see the package here:
https://launchpad.net/~couchdb/+archive/stable
It's also under /dev, but I believe that's going to be moved out to
make room for 1.6 at some point.
Cheers,
Eli
On Sun, Feb 16, 2014 at 3:33 PM, Benoit Chesneau wrote:
> On Mon, Feb 17, 2014 at 12:18 AM, meredrica wro
Thanks for working with us Dave, it was a pleasure. And I'm glad to
see that people are excited about the end result.
While I can't commit to anything right now, I'm going to be pushing my
company to sponsor more of these in the future. It probably won't be
every release (our product release cyc
On Tue, Dec 3, 2013 at 10:20 AM, Benjamin Young wrote:
> Sphinx (for one...among many...), uses "_*" prefixed folders for it's
> styles, templates, etc. So does Github's ghpages.
...
> The point with "/_/" was to narrow the surface area of the API.
I'd like to point out that if the goal is to red
Hello all,
My company is interested in getting a modern version of CouchDB packaged up
for Ubuntu 12.04 LTS. We don't have any in-house expertise, but we're able
the sponsor the work needed to make this happen. I'm hoping that we can
find someone who can accomplish this and is available for cont
When I unzip the file, the Apache CouchDB app claims it's from Aug 29th,
3:05pm. I can't tell if that's my fault somehow, or from the .zip file.
However, it opens fine, shows 1.5.0 as the version, and verify install
works fine.
ISTR binaries don't get voted on, so instead of +1 I'll just say:
\
I'll second Jason Smith. Having a simple, clear way to insure that a
replication has caught up is important, and async polling isn't going to be
performant enough for some applications.
That said, having that way be something related to the _replicator db would
be fine. I'm not attached to the c
I have recently upgraded to 10.8, and I had to right click -> open to get
it to run, since this wasn't built by a known entity. I also had to "Open
Admin Console" from the icon in the top bar, but otherwise it looks fine
(verify installation worked).
Is it possible to get at Fauxton with this bui
Speaking as someone who's used git-flow in a small-corporate context (and
not as someone who is likely to be contributing overmuch, so huge grains of
salt), I'd like to make a couple of observations:
- Git flow also presumes that the integration branch ("develop" according
to the defaults, though
On Mon, Mar 18, 2013 at 11:21 AM, Benoit Chesneau wrote:
> Thanks for the info! Sounds like it would allows to have a 2-way
> channel. not so trivially I guess but possible :)
>
What isn't trivial about it, in your mind? To me, it seems like including
an email on the CC list is about as trivial
Every single email I get from a github pull request contains a header like:
Reply-To: mobius-medical/dev <
reply+p-111-0123456789abcdef-...@reply.github.com>
And sending email to that email address causes the content of that email to
show up in the pull request.
Unless public repos behave differ
On Fri, Mar 15, 2013 at 9:47 AM, Noah Slater wrote:
> Note to the list. I am flagging this thread as something to distill into
> our community guide. I think it's important we talk about this somewhere
> that is a little less easy to loose than a mailing list post.
I suspect that you've hit the
Is there a clear statement on if we should expect the futon tests to pass
under OSX using the precompiled binaries?
I'm intending to to try the OSX binaries when I have a moment, but it feels
like there's some mixed messaging about if we should expect the tests to
work (Jan's mail just says to use
Works for me. +1.
Eli
On Mon, Feb 18, 2013 at 3:52 PM, Jan Lehnardt wrote:
> And fixed a linker issue that was brought up on user@
>
> http://people.apache.org/~jan/dist/packages/mac/1.2.1/
>
> Cheers
> Jan
> --
>
>
>
> On Feb 18, 2013, at 01:38 , Jan Lehnardt wrote:
>
> > Ok, back to us
ituation correctly, there isn’t much we can do other than
> prodding
> other projects.
>
> Best
> Jan
> --
>
>
>
> On Feb 14, 2013, at 19:24 , "Eli Stevens (Gmail)"
> wrote:
>
> > As best I can recall, I did the following under OSX 10.7.5:
> >
As best I can recall, I did the following under OSX 10.7.5:
- Download the .zip
- Decompress it
- Copy it to applications
- Doubleclick Apache CouchDB to start it
- Ran a test script that I have for a library of mine (that's all of the
couchable stuff in the logs), which worked fine.
- Poked aroun
On Thu, Nov 1, 2012 at 9:28 PM, Adam Kocoloski wrote:
> Hi Eli, Benoit linked to a variant of it in the beginning of this thread.
> There's a lot to like about it, and most of it is very similar to the
> workflow we're converging on in this project. The big difference is that in
> git-flow th
Are the committers familiar with git-flow?
http://nvie.com/posts/a-successful-git-branching-model/
https://github.com/nvie/gitflow
Having used it at work for closed-source projects, I recommend it as
the script support is nice, and it provides a decent branching model
that "just works." While we
Speaking only as a lurker on the dev list, I am -1 on moving commits
off to a new list. JIRA threads are easy to filter into a different
folder if desired, and being able to see project activity is nice.
If any change is to be made, I would like to see the JIRA email
subjects/threading changed so
On Thu, Sep 27, 2012 at 1:02 PM, john.tiger wrote:
> look, if it was a simple markdown text file download, I'd already be reading
I don't think that a project with the scope of CouchDB is ever going
to be well served by "simple" documentation.
> and making updates instead of f.. ing around tryin
On Tue, Sep 25, 2012 at 10:25 PM, Ryan Ramage wrote:
> 1) We have to decide on the directory structure. Based on what benoit
> and dale have brought up. I have opinions, along with others. Lets not
> rattle sabres around this yet. But pick something relatively user
> friendly, and straightforward
I've reported the brew issue here:
https://github.com/mxcl/homebrew/issues/12633
I don't think it's directly related to couchdb, just blocking it.
Eli
On Fri, Jun 8, 2012 at 11:55 AM, Dave Cottlehuber wrote:
> On 8 June 2012 18:40, Eli Stevens (Gmail) wrote:
>
>&
On Fri, Jun 8, 2012 at 7:31 AM, Hans J Schroeder wrote:
> @Benoit
> I prefer to use only the well known port 5984.
Speaking only as an end-user, I agree that the well-known port should
be the default.
While this comes as a bit late to the party, the release seems to be
working for me (I haven't
On Fri, May 11, 2012 at 7:57 AM, CGS wrote:
> What I don't understand is the followings:
> 1. Those guys wanted a single front-end server which should keep up with
> the incoming requests, correct? As far as I understood, CouchDB philosophy
> is based on safety of the data, which was implemented a
I think that much of the disagreement stems from different audience /
use cases in mind when proposing changes to the web site. I see a few
main user profiles that visitors to the website could be lumped into:
- Neophyte users who are looking for information about CouchDB to see
if it interests t
I'd like to offer what little I've done to measure attachment speeds:
https://github.com/wickedgrey/couchdb-attachment-speed
It's in python, but might be useful as an example of what to test.
I've explained in more detail in this user@ mailing list thread:
http://mail-archives.apache.org/mod_mbo
72 matches
Mail list logo