On Mon, Jan 31, 2011 at 21:50, Jan Lehnardt wrote:
> IMHO, the general rule is supporting the current and previous release. We
> have referred to that rule in the past. I'm not sure that is written down
> anywhere though. I think this is a good policy either way.
>
> We planned to have 1.0.2 and
[
https://issues.apache.org/jira/browse/COUCHDB-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989024#comment-12989024
]
joel reed commented on COUCHDB-867:
---
I can't think of any security implications - you s
[
https://issues.apache.org/jira/browse/COUCHDB-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
joel reed updated COUCHDB-867:
--
Attachment: handle_file_req.diff
requested diff
> Add http handlers for root files with special meani
[
https://issues.apache.org/jira/browse/COUCHDB-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988943#comment-12988943
]
Paul Joseph Davis commented on COUCHDB-562:
---
I thought your birthday was last w
[
https://issues.apache.org/jira/browse/COUCHDB-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds updated COUCHDB-562:
--
Attachment: 0002-prevent-excessive-linking-of-mozjs-COUCHDB-1033.patch
0001-lin
[
https://issues.apache.org/jira/browse/COUCHDB-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds updated COUCHDB-562:
--
Attachment: (was:
0001-link-couchjs-w-mozjs-use-pkg-config-COUCHDB-562.patch)
> link couc
[
https://issues.apache.org/jira/browse/COUCHDB-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds updated COUCHDB-1033:
---
Issue Type: Sub-task (was: Improvement)
Parent: COUCHDB-562
> prevent excessive li
Hello all,
I think the most important thing is to have a policy and make clear to end
users what it is. I don't care about 0.11.x personally since we're still on
0.10.1 in production (which has been rock solid for us I might add) and are
probably upgrading to 1.0.2 soon (or 1.1.0 if that's rele
[
https://issues.apache.org/jira/browse/COUCHDB-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana updated COUCHDB-1051:
---
Attachment: COUCHDB-1051.patch
> Replicator DB: make number of replication retry attempts c
Replicator DB: make number of replication retry attempts configurable
-
Key: COUCHDB-1051
URL: https://issues.apache.org/jira/browse/COUCHDB-1051
Project: CouchDB
Issue Type
On 31 Jan 2011, at 21:09, Noah Slater wrote:
>
> On 31 Jan 2011, at 15:05, Nils Breunese wrote:
>
>> I saw CouchDB 1.0.2 fixes a security issue. Am I right that 0.11.x won't get
>> this fix? Is there an official statement somewhere on what 'series' of
>> releases are currently supported?
>
>
On 31 Jan 2011, at 20:55, Filipe David Manana wrote:
> Hi,
>
> In 1.1.x we have a new configuration option named "nodelay" under the
> the "httpd" section.
> However, COUCHDB-1008 adds the option "socket_options" which is more
> generic, allowing nodelay to be specified there amongst other socke
[
https://issues.apache.org/jira/browse/COUCHDB-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988878#comment-12988878
]
Bob Dionne commented on COUCHDB-462:
Here's a new version that only walks the revisio
On Mon, Jan 31, 2011 at 3:09 PM, Noah Slater wrote:
>
> On 31 Jan 2011, at 15:05, Nils Breunese wrote:
>
>> I saw CouchDB 1.0.2 fixes a security issue. Am I right that 0.11.x won't get
>> this fix? Is there an official statement somewhere on what 'series' of
>> releases are currently supported?
On 31 Jan 2011, at 15:05, Nils Breunese wrote:
> I saw CouchDB 1.0.2 fixes a security issue. Am I right that 0.11.x won't get
> this fix? Is there an official statement somewhere on what 'series' of
> releases are currently supported?
I would have said that anything we list on the downloads.ht
[
https://issues.apache.org/jira/browse/COUCHDB-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988869#comment-12988869
]
Paul Joseph Davis commented on COUCHDB-867:
---
Joel,
Can you attach a copy of th
On Mon, Jan 31, 2011 at 2:55 PM, Filipe David Manana
wrote:
> Hi,
>
> In 1.1.x we have a new configuration option named "nodelay" under the
> the "httpd" section.
> However, COUCHDB-1008 adds the option "socket_options" which is more
> generic, allowing nodelay to be specified there amongst other
Hey guys,
I saw CouchDB 1.0.2 fixes a security issue. Am I right that 0.11.x won't get
this fix? Is there an official statement somewhere on what 'series' of releases
are currently supported?
Nils (not a dev@ member, please CC: me).
--
Here's a fix for bug 867:
https://github.com/joelwreed/couchdb/commit/528c52e6517b777f22fee0ab7fb0f7977c4c05c2
It adds a new handler, handle_file_req, to serve up files like
/crossdomain.xml from a couchdb instance. For example, you could add:
[httpd_global_handlers]
crossdomain.xml = {cou
Hi,
In 1.1.x we have a new configuration option named "nodelay" under the
the "httpd" section.
However, COUCHDB-1008 adds the option "socket_options" which is more
generic, allowing nodelay to be specified there amongst other socket
options.
My concern is that having "nodelay" as an isolated opti
What's the warning that dialyzer throws?
On Mon, Jan 31, 2011 at 6:07 AM, Robert Dionne
wrote:
> Thanks Adam,
>
> I also had broken up 988 to move some into 902 and the rest into 462. I'll
> rearrange things based on this commit.
>
> One question I have is about a re-factor I did in 988 involv
Dialyzer doesn't warn about this coding pattern when I run it, and I'm somewhat
partial to the way it is now. It's not much of an issue in this particular
statement, but when we have nested case/try/if clauses it can be difficult to
figure out the possible values that the variable can take if i
[
https://issues.apache.org/jira/browse/COUCHDB-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988771#comment-12988771
]
joel reed commented on COUCHDB-867:
---
Here's a fix for this issue:
https://github.com/j
[
https://issues.apache.org/jira/browse/COUCHDB-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988764#comment-12988764
]
Petr Běhan commented on COUCHDB-708:
Still a problem in current couchdb version (1.0.
[
https://issues.apache.org/jira/browse/COUCHDB-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski closed COUCHDB-902.
--
Resolution: Fixed
Fix Version/s: 1.2
> Attachments that have recovered from conflict do
still a good idea, I think I have a version that does this short-circuiting.
Makes you want Scheme's call/cc :)
On Jan 30, 2011, at 2:01 PM, Adam Kocoloski (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/COUCHDB-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment
Thanks Adam,
I also had broken up 988 to move some into 902 and the rest into 462. I'll
rearrange things based on this commit.
One question I have is about a re-factor I did in 988 involving multiple
assignments to a variable[1]. This re-factor does nothing to change the
behavior of the co
All replications breaks on failed compaction (with different DBs)
-
Key: COUCHDB-1050
URL: https://issues.apache.org/jira/browse/COUCHDB-1050
Project: CouchDB
Issue Type: Bug
28 matches
Mail list logo