only first token in key with '*'
Key: COUCHDB-1348
URL: https://issues.apache.org/jira/browse/COUCHDB-1348
Project: CouchDB
Issue Type: Bug
Components: Infrastructure
Affects Versions: 1.1.1
[
https://issues.apache.org/jira/browse/COUCHDB-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson updated COUCHDB-1348:
---
Component/s: (was: Infrastructure)
HTTP Interface
Labels:
[
https://issues.apache.org/jira/browse/COUCHDB-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13157464#comment-13157464
]
Filipe Manana commented on COUCHDB-1289:
Looks good Bob, only a small regression
[
https://issues.apache.org/jira/browse/COUCHDB-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13157473#comment-13157473
]
Bob Dionne commented on COUCHDB-1289:
-
Thanks for the review Filipe. I pushed your
On Sat, Nov 26, 2011 at 6:09 AM, Kristina Schneider
m...@kristinaschneider.com wrote:
Whatever you are voting on, happy to see some activity on these old
designs getting implemented :)
Noah, let me know if / how I can help and I'll see if I can free up some
hours for that!
Kriesse
On
[
https://issues.apache.org/jira/browse/COUCHDB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana updated COUCHDB-188:
--
Attachment: 0001-Allow-doc-delete-and-creation-in-the-same-bulk-updat.patch
Attaching patch
[
https://issues.apache.org/jira/browse/COUCHDB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana reassigned COUCHDB-188:
-
Assignee: Filipe Manana
_bulk_docs fails when deleting and adding a doc with the
[
https://issues.apache.org/jira/browse/COUCHDB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana updated COUCHDB-188:
--
Attachment: 0001-Allow-doc-delete-and-creation-in-the-same-bulk-updat.patch
_bulk_docs
[
https://issues.apache.org/jira/browse/COUCHDB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana updated COUCHDB-188:
--
Attachment: (was:
0001-Allow-doc-delete-and-creation-in-the-same-bulk-updat.patch)
[
https://issues.apache.org/jira/browse/COUCHDB-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana updated COUCHDB-911:
--
Fix Version/s: (was: 1.2)
1.3
Same ocurrence of a document in
Let's forget about the format or the toolchain for now, they're bikesheds.
What is the goal of this effort?
We want documentation in the source, sure. But why? What kind of
documentation is it going to be? What topics will it cover? Can anyone come
up with a suggested outline for it? i.e. Table
For me, the goal would be for docs/ to contain at least a brief
description of every couchdb feature. I specifically don't expect to
see introductory text, example views, tutorials, etc, except where
needed to describe core features. One thing we've missed for a long
time, and Couchbase had to
That sounds reasonable. The sort of thing you'd get in an appendix, if this
were a book. A blow by blow description of each CouchDB feature, config
variable, URL parameter, etc.
Seeding the wiki is a problem. The documentation should live in one place,
and one place only. Seeding the wiki is a
On 26 November 2011 05:43, Noah Slater nsla...@tumbolia.org wrote:
These two projects are orthogonal to each other:
Project 1: Getting code/API docs bundled in the source distribution.
Project 2: Getting a new website design in place.
On Sat, Nov 26, 2011 at 1:36 AM, Marco Monteiro
On 26 November 2011 14:25, Robert Dionne dio...@dionne-associates.com wrote:
+1 for Latex
Hi Robert, all,
Thanks for taking the time to read all that!
Specific design tools aside, are you willing to support at least the
principle of upgrading/improvement of the documentation?
Or are you
Noah: All I really mean is that the docs/ are widely available. If
it's infeasible to push them to the wiki then let's not do it, but I'd
be surprised if that's a technical challenge for a group with our
diverse superpowers.
As for choice of markup language, I have no preference. What's the
Sure.
Well, I'd like to link to the docs from the website. And some amount of
basic typesetting would be nice. HTML is the bare minimum if we want text
(obviously) and hyperlinks. I think hyperlinks would be useful. Even if
it's only so we can use anchors.
If you look at the source of the
I am not sure if it will bring much into our discussion, but I found
this view on Github very interesting so I thought I should post it:
http://zbowling.github.com/blog/2011/11/25/github/
Cheers
Christian
--
http://www.grobmeier.de
https://www.timeandbill.de
On Nov 26, 2011, at 2:47 PM, Dave Cottlehuber wrote:
On 26 November 2011 14:25, Robert Dionne dio...@dionne-associates.com wrote:
+1 for Latex
Hi Robert, all,
Thanks for taking the time to read all that!
Specific design tools aside, are you willing to support at least the
[
https://issues.apache.org/jira/browse/COUCHDB-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13157615#comment-13157615
]
Bob Dionne commented on COUCHDB-1289:
-
Add etap test for this last case[1]
[1]
On Sat, Nov 26, 2011 at 11:41, Noah Slater nsla...@tumbolia.org wrote:
That sounds reasonable. The sort of thing you'd get in an appendix, if this
were a book. A blow by blow description of each CouchDB feature, config
variable, URL parameter, etc.
Seeding the wiki is a problem. The
I will happily volunteer to work on generating html output from whatever we
store the documentation in, ultimately I think they should be integrated
into futon, and I would request that whatever the documentation is stored
in, that its its reasonably easy to parse and wrangle into your own output
On Sat, Nov 26, 2011 at 14:42, Dale Harvey d...@arandomurl.com wrote:
I will happily volunteer to work on generating html output from whatever we
store the documentation in, ultimately I think they should be integrated
into futon, and I would request that whatever the documentation is stored
Cool idea.
Just to re-iterate, we should keep things as simple as possible for now. I
think we can get away with maintaining a set of easy to read, easy to edit
HTML files that are served up along with Futon. These would be kept in the
source exactly the the current set of HTML files that make up
Also, Bob, you mention Couchbase stepped in to fill this gap.
Do you know where we can see the fruits of that labour? If licensing
permits, we might find it useful to take that as a starting point, or at
least reference the sections there as we can reference parts of the
existing wiki, while
Hi, Devs.
I just finished talking with dch a bit about our latest perspective on
raising contribution workflow to the next level in light of the git
migration and the documentation discussion.
Here's a summary of my observations:
* Having documentation in the source raises the problem that,
[
https://issues.apache.org/jira/browse/COUCHDB-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13157634#comment-13157634
]
Randall Leeds commented on COUCHDB-431:
---
I wanted to bump this discussion again so
[
https://issues.apache.org/jira/browse/COUCHDB-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13157643#comment-13157643
]
Jason Smith commented on COUCHDB-431:
-
The patch remains a significant security
[
https://issues.apache.org/jira/browse/COUCHDB-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13157649#comment-13157649
]
Jason Smith commented on COUCHDB-431:
-
Rebased my patch set to Randall's new branch:
[
https://issues.apache.org/jira/browse/COUCHDB-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13157695#comment-13157695
]
Benoit Chesneau commented on COUCHDB-431:
-
@tilgovi thanks to bump the again. I
30 matches
Mail list logo
